LOGIN   :::   RECOVER PASS   :::   GET ACCOUNT    
Browse
  • Projects
  • Code (CVS)
  • Forums
  • News
  • Articles
  • Polls
  •  
    OpenCores
  • FAQ
  • CVS HowTo
  • Mission
  • Media
  • Tools
  • Advertise
  • Mirrors
  • Logos
  • Contact us
  • Find Resources
  • Job Opportunity
  •  
    Tools
  • Search
      
  • Download Cores (CVSGet)
  •  
    More
  • Wishbone
  • Perlilog
  • EDA tools
  • OpenTech CD
  •  
    Navigation: All forums > Openrisc > Message List > Message Post

    Message

    Reply | Reply all
    Date Prev | Date Next | Thread Prev | Thread Next Date Index | Thread Index

    From: =?unknown-8bit?Q?Gy=F6rgy?= 'nog' Jeney<nog@s...>
    Date: Mon Feb 21 15:03:03 CET 2005
    Subject: [openrisc] x86_64 linux [more&more]
    Top
    > > this is an interesting diff between i386 and x86-64 generated assembly...
    > > the 268435456 just happens to be 0x10000000, so it's the upper part of
    >
    > No, it takes the whole 64 bit part, not just the upper or lower.
    >
    > > 1152921504606846976. My really wild guess would be that some code assumes
    > > target register size = host register size...
    > Yes, something like. Would be nice to know where, and to constrain this to 32 bit lower part,
    > and ignore in rest. Who write these piece of code in /or32 ?

    If it is really that only the low 32 bits gets written to some 64-bit variable
    and the rest is left uninitialised, I would say that it is worth a try to run
    gcc through valgrind. It should pinpoint this error with ease.

    nog.

     
    Copyright (c) 1999 OPENCORES.ORG. All rights reserved.