From mboxrd@z Thu Jan 1 00:00:00 1970 From: "John David Anglin" To: manfred.h@gmx.net Cc: gcc-bugs@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: Segmentation fault building libg++ without named returns Date: Sat, 09 Sep 2000 15:06:00 -0000 Message-id: <200009092206.SAA12592@hiauly1.hia.nrc.ca> References: <14778.14256.660882.299239@saturn.hollstein.net> X-SW-Source: 2000-09/msg00320.html > Thanks for the patch you sent with your previous email; I observed the > same failures when Mark installed his patch to warn about using named > return values. I took a differend approach than you, i.e. instead of > removing the code completely, I used the opposite logic with a flag > _G_USE_NRV as opposed to the former _G_NO_NRV; I've attached that > patch to this email. I tend to think the code should be removed. There were essentially two sets with the "same" code. However, the unused branch which didn't use named returns had rotted a bit. Apparently, `and', `or' and `xor' are c++ diagraphs and can't be used. > Regarding the missing weak symbols, I'm pretty much at a loss; > building Fix.cc and Rational.cc doesn't generate all required weak > symbols as it did before; even worse, using a reduced test case > doesn't fail to generate those symbols... I'll dig further and keep > you informed. I don't have any time this weekend to work on it but I think a first step would be to dump the assembly code for Fix.cc and see what is happening with respect to the week definitions. Then, looking at the rtl may help to pinpoint where things are going wrong. It's a fairly recent change to the compiler that has caused the problem. Dave -- J. David Anglin dave.anglin@nrc.ca National Research Council of Canada (613) 990-0752 (FAX: 952-6605)