dwarf2out & var-tracking & cond_exec call

2013-11-29 Thread BELBACHIR Selim
Hi, I'm still porting my private backing from gcc 4.5.2 to gcc 4.7.3. When compiling the following code with -g option, I encountered "internal compiler error: in dwarf2out_var_location, at dwarf2out.c:20883" void toto(int* , float); void foo(int a, float b, int * c) { if (b) toto(c, b);

RE: dwarf2out & var-tracking & cond_exec call

2013-11-29 Thread BELBACHIR Selim
I found my problem totally elsewhere (sorry to bother) I was loosing proper NOTES during a COND_EXEC((..)(CALL(..))) split ... Selim -Message d'origine- De : gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] De la part de BELBACHIR Selim Envoyé : vendredi 29 novembre 2013 14:29 À 

Re: infrastructure to detect whether code originates from macro expansion

2013-11-29 Thread Dodji Seketeli
Hello Robert, Robert Schiele a écrit: > in http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48778 Manuel > López-Ibáñez mentioned that starting with gcc 4.7 there is supposed to > be infrastructure to figure out for diagnostics whether the location > of an error was created by macro expansion and tha

Ada Indefinite_Holders

2013-11-29 Thread Christian Morgenroth
Hello, Would you mind to implement the function Ada.Containers.Indefinite_Holders.Reference (Container : aliased in out Holder) return Reference_Type; please? Best regards Christian Morgenroth

Getting LD warnings on Mac OS X

2013-11-29 Thread Kevin Ingwersen
Hello there! I am trying to compile GCC using Apple’s latest tools. The reason is that I am building an own, redistributable, toolchain. Everything goes quite well (except a ton of warnings about redeclarations and c99 standart), untill it tries to link cc1. A rough rip-off of the warnings is: