http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20366
Peter O'Gorman pogma at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
--
pogma at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo|unassigned at gcc dot gnu |pogma at gcc dot gnu dot org
|dot org
--- Comment #20 from rwild at gcc dot gnu dot org 2008-03-07 06:54 ---
Subject: Bug 20366
Author: rwild
Date: Fri Mar 7 06:53:59 2008
New Revision: 133001
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=133001
Log:
fixincludes/
2008-03-07 Peter O'Gorman [EMAIL PROTECTED]
--- Comment #19 from bugzilla-gcc at thewrittenword dot com 2008-03-03
21:12 ---
Proposed patch:
http://gcc.gnu.org/ml/gcc-patches/2008-03/msg00162.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20366
--- Comment #17 from peter at pogma dot com 2007-12-31 19:28 ---
(In reply to comment #16)
This was also a problem on solaris:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=4850
I mean
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=4886
--
peter at pogma dot com changed:
--- Comment #18 from bugzilla-gcc at thewrittenword dot com 2007-12-31
19:39 ---
(In reply to comment #16)
Because it is not currently possible to build an autoconf based project on aix
with gcc without doing --disable-largefile, we would like to see this fixed.
More accurately, it
--- Comment #14 from tcoleman at autowares dot com 2007-12-22 20:18 ---
(In reply to comment #12)
I don't see it as so much a matter of focus.
A lot of applications test for _LARGE_FILES in the C library and will set it as
a configuration option if supported. As far as straight C
--- Comment #15 from dje at watson dot ibm dot com 2007-12-22 20:52 ---
Subject: Re: AIX g++ -D_LARGE_FILES fails to compile #include iostream
tcoleman at autowares dot com writes:
Tom Does G++ really have to be either one way or the other? Can't it also
include
Tom conditional
--- Comment #10 from dje at watson dot ibm dot com 2007-12-21 14:58 ---
Subject: Re: AIX g++ -D_LARGE_FILES fails to compile #include iostream
Why is this? -D_LARGE_FILES simply enables LFS. xlC works with and without
-D_LARGE_FILES. Shouldn't G++ work as effectively as xlC?
--- Comment #11 from bugzilla-gcc at thewrittenword dot com 2007-12-21
19:14 ---
(In reply to comment #10)
Subject: Re: AIX g++ -D_LARGE_FILES fails to compile #include iostream
xlC has its own system header files. G++ needs to use the AIX
system header files with
--- Comment #12 from dje at gcc dot gnu dot org 2007-12-21 23:23 ---
If AIX G++ users are focussing on 64-bit apps and large files, I'm willing to
switch the default to _LARGE_FILES. The changes would be in
gcc/config/rs6000/aix*.h CPP_SPEC and libstdc++/config/os/aix/os_defines.h,
--- Comment #13 from bugzilla-gcc at thewrittenword dot com 2007-12-21
23:25 ---
(In reply to comment #12)
If AIX G++ users are focussing on 64-bit apps and large files, I'm willing to
switch the default to _LARGE_FILES. The changes would be in
gcc/config/rs6000/aix*.h CPP_SPEC and
--- Comment #8 from dje at gcc dot gnu dot org 2007-12-21 00:29 ---
The issue is whether to default G++ to _LARGE_FILES, as is done for Fortran,
and perform all libstdc++ I/O as 64-bit operations, which will affect
performance. Not everyone may want or need large I/O. There is no way
--- Comment #9 from bugzilla-gcc at thewrittenword dot com 2007-12-21
03:59 ---
(In reply to comment #8)
The issue is whether to default G++ to _LARGE_FILES, as is done for Fortran,
and perform all libstdc++ I/O as 64-bit operations, which will affect
performance. Not everyone may
--- Comment #5 from haubi at gentoo dot org 2007-12-19 15:57 ---
Created an attachment (id=14796)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14796action=view)
the effect fixincludes could have on aix5.2/aix5.3
When applying this patch to (already fixed) stdio.h on
--- Comment #6 from tcoleman at autowares dot com 2007-12-20 00:06 ---
The test program will compile if you comment out the #undefs in cstdio.
//#undef fgetpos
//#undef fopen
//#undef freopen
//#undef fsetpos
I've wrestled with this problem with G++ on AIX for years. In desparation
--- Comment #7 from dsanderson at panasas dot com 2007-12-20 00:17 ---
Note that my originally stated workaround -- to compile with -maix64 -- doesn't
really work beyond helping the compile to succeed. Using -maix64 gives you a
64-bit executable (e.g. with 64-bit pointers and a 64-bit
--- Comment #4 from haubi at gentoo dot org 2007-12-01 22:04 ---
Same here with gcc-4.2.2 and powerpc-ibm-aix5.3.0.0.
Some diagnostics what happens when _LARGE_FILES (and _LARGE_FILE_API) is
defined:
sys/types.h
/* would both be 'long' without _LARGE_FILES: */
typedef long long
--- Comment #3 from bugzilla-gcc at thewrittenword dot com 2006-02-22
23:43 ---
Any plans to add _LARGE_FILES support to g++/libstdc++ for AIX?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20366
--
What|Removed |Added
Component|c++ |target
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20366
--- Additional Comments From dje at gcc dot gnu dot org 2005-03-07 19:30
---
G++ and libstdc++ on AIX currently is configured to enable _LARGE_FILE_API,
but not _LARGE_FILES. _LARGE_FILE_API exposes the 64-bit functions with
separate names off64_t and fopen64(), but does not redefine
21 matches
Mail list logo
