[Bug c++/12511] When building with -O2 getsockname may fail

[john dot phelps at solipsys dot com]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12511



------- Additional Comments From john dot phelps at solipsys dot com  2003-10-06 12:46 -------
Subject: RE:  When building with -O2 getsockname may fail


A coworker pointed out to me that the problem was seen w/gcc 3.3, not 3.3.1,
because of build/install issues with 3.3.1 under RedHat 9. In any case, will
there be, or is that currently, a patch released for 3.3.x to fix the
problem? We have just recently switched over to using 3.3.1 and would like
to stay on track with this version for awhile.

Alternatively, is there a good reason to switch over to 3.4 as opposed to
sticking with 3.3.1? We have been using 2.95.3 for years now and had to drag
people kicking and screaming into the 3.3 release. I would like to stick
with this version unless there is a compelling reason not to do so.

Thanks.

--
John Phelps            http://www.solipsys.com
Solipsys Corporation   mailto:john.phelps@solipsys.com

 


-----Original Message-----
From: pinskia at gcc dot gnu dot org [mailto:gcc-bugzilla@gcc.gnu.org] 
Sent: Saturday, October 04, 2003 7:38 PM
To: john.phelps@solipsys.com
Subject: [Bug c++/12511] When building with -O2 getsockname may fail

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12511



------- Additional Comments From pinskia at gcc dot gnu dot org  2003-10-04
23:37 -------
I can reproduce this under 3.3.1 (20030707) but it is fixed for 3.4 but this
might be a glibc 
problem though.



------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.