![]() ![]() > For platforms using the Linux unwind ABI: _libunwind_Unwind_Backtrace: Alias of _Unwind_Backtrace I hoped that maybe we could do it in the future. > It turns out that it wouldn't be easy for the reasons you have > gcc and icc with either gcc or icc as driver to create executables. > At first, I thought it would be nice to mix. > to the generating compiler and the personality routine it chose > Why are you specifying this at all? The LSDA is entirely private For C++, it will be _gnu_linux_cxx_personality_v0. For C, it will be _gnu_linux_c_personality_v0. An implementation of GNU/Linux compiler shall provide the personality > I'm certain I don't want to get into this, but. > to provide the binary compatibilty when the 3rd part unwind library > The current unwind specification for GNU/Linux/ia64 does't specify how > On Thu, at 04:50:51PM -0700, Richard Henderson wrote: Subject: RFC: The unwind specification draft for GNU/Linux/ia64 I always end up missing the key-signing "parties". >(Mark, I noticed that on the public key servers your key does not seem to ![]() >complete your information, Gaby and Mark. >I went ahead and committed the patch below, as an initial attempt please ![]() >Yes, even though this only applies to (and not ) >and I believe all of them have signed GGC tarballs as of today. >be those of people "authorized" to upload GCC on >That looks to me to be a good suggestion - the keys would >Ideally with Mark's key fingerprint included. >Perhaps we could put this information on the website somewhere? prefix=$HOME -enable-languages=c++ -enable-shared -disable-nls c /home/gdr/redhat/4.gcc/gcc/crtstuff.c -DCRT_BEGIN \ I/home/gdr/redhat/4.gcc/gcc/./include -g0 -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-unit-at-a-time -fno-omit-frame-pointer \ ![]() I/home/gdr/redhat/4.gcc/gcc -I/home/gdr/redhat/4.gcc/gcc/. home/gdr/build/4/gcc/xgcc -B/home/gdr/build/4/gcc/ -B/home/gdr/i686-pc-linux-gnu/bin/ -B/home/gdr/i686-pc-linux-gnu/lib/ -isystem /home/gdr/i686-pc-linux-gnu/include -isystem /home/gdr/i686-pc-linux-gnu/sys-include -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem. The experiment isn't conclusive :-(Ĭc1 (built by mainline) seems to go into an infinite loop for an hour now. I just tried a build a fresh update of gcc-3_4-branch with CVS GCC Subject: Compiling GCC-3.4.x with mainline: Infinite loop? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |