------- Comment #5 from pcarlini at suse dot de 2007-07-09 21:19 -------
(In reply to comment #4)
> >Comment #2 From Andrew Pinski 2007-07-09 02:53 [reply] -------
> >No include for <string.h> or <cstring>.
>
> Andrew, I'm not an expert at C++ but I did my best to attempt to make a couple
> of reduced testcases where I felt I was able. BOTH those testcases _do_ use
> "#include <string>".
That header has *nothing* to do with <cstring> and <string.h>
> There exists TWO issues not dealt with in your replies (see above):
>
> 1): "There is something about the way GCC 4.3 builds "gij" that does not let
> it
> run .jar files that work perfectly on the WinXP platform with Internet
> Explorer."
>
> 2): The ".ii" files that GCC produces are not 'all inclusive' - you can't move
> them and then simply compile them in a different directory (like ".i" files).
> How are we supposed to create an ".ii" file and attach it for an expert to
> study? (as is suggested we do for "C" errors and ".i" files). Maybe the
> streamlining has caused this
The last issue simply doesn't make sense. The former at best is a separate Java
issue.
--
pcarlini at suse dot de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32683
