[Bug libgcj/27219] bogus-looking code in natPlainSocketImplPosix.cc

2016-09-30 Thread pinskia at gcc dot gnu.org 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27219

Andrew Pinski  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #4 from Andrew Pinski  ---
Closing as won't fix as libgcj (and the java front-end) has been removed from
the trunk.

[Bug libgcj/27219] bogus-looking code in natPlainSocketImplPosix.cc

2006-04-20 Thread tromey at gcc dot gnu dot org 


--- Comment #1 from tromey at gcc dot gnu dot org  2006-04-20 15:54 ---
You can see it by compiling this short example
program with 'g++ --syntax-only':

#include gcj/cni.h
#include jni.h


-- 

tromey at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1
   Last reconfirmed|-00-00 00:00:00 |2006-04-20 15:54:03
   date||


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

[Bug libgcj/27219] bogus-looking code in natPlainSocketImplPosix.cc

2006-04-20 Thread tromey at gcc dot gnu dot org 


--- Comment #2 from tromey at gcc dot gnu dot org  2006-04-20 16:06 ---
Ignore that, I appended to the wrong report.


-- 


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

[Bug libgcj/27219] bogus-looking code in natPlainSocketImplPosix.cc

2006-04-20 Thread mckinlay at redhat dot com 


--- Comment #3 from mckinlay at redhat dot com  2006-04-20 21:45 ---
It does look like these should be made robust in the case of an EINTR which was
caused by a signal other than the interrupt signal.

As for ignoring ENOTCONN and ECONNRESET, I have a vague recollection that there
is a good reason for doing this (compatibility with Sun?) - but this probably
does warrant more testing/investigation, and a better comment.


-- 


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