On 03/09/2010 05:11 PM, Thomas Martitz wrote: > Am 09.03.2010 17:41, schrieb Andrew Haley: >> On 03/09/2010 04:30 PM, Thomas Martitz wrote: >> >> >>> EABI IIRC only mentions changed rules for passing 64bit types. This call >>> should have been the same with 4.4.3. It eventually is if the parameters >>> are in a different order. >>> >>> If this is really a gcc bug, how should we proceed? I assume a bug >>> report on bugzilla? >>> >> This is very strange. Can you make a self-contained source file >> that shows the problem on its own? We need to be able to try it. >> It doesn't have to run, we just have to see the source it >> generates. > > I tried, but the following code doesn't show this problem :( That does not surprise me. I think you're seeing a problem that is caused by something elsewhere in your program. I'm guessing that there may be a bad prototype or somesuch. I think you need to strip down your sources until you find something. Maybe you should try -save-temps and have a look at the actual preprocessd source. Maybe some bastard has done #define int long or something evil like that! Andrew.
