This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Then maybe it's due to one of these files in patches/gcc-3.3.3:
I can try removing them and building and will also look at what each of them does.
Also, I'm assuming you're simply building the toolchain, then compiling a simple testcase by hand, rather than running the >whole testsuite.
Yes, I am simply building the toolchain and running single testcase by hand using:
DEJAGNU=~/ixos/linux2.6/linux/3rdParty/crosstool/crosstool-0.28-rc19/boards/master.exp PATH=~/ixos/linux2.6/linux/3rdParty/crosstool/crosstool-0.28-rc19/result/dejagnu/bin/:$PATH \ runtest --tool=gcc --target=powerpc-750-linux-gnu -v -v -v -v -a execute.exp=struct-ret-1.c
Or compiling using "~toolDir/powerpc-750-linux-gnu-gcc [flags] struct-ret-1.c" and then transferring it to the target.
OK, I'd like to take the latter approach. Which flags do you use when building struct-ret-1.c, or are the default flags sufficient to show the problem? - Dan
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |