[Bug target/61099] Mac 2GB file limit error

2014-11-03 Thread fxcoudert at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61099

Francois-Xavier Coudert fxcoudert at gcc dot gnu.org changed:

   What|Removed |Added

 Status|WAITING |RESOLVED
 CC||fxcoudert at gcc dot gnu.org
 Resolution|--- |INVALID

--- Comment #8 from Francois-Xavier Coudert fxcoudert at gcc dot gnu.org ---
The assembler issue was submitted to Apple as bug #18860674. I don't have high
hopes, but I don't think there's much more we can do.

For completude: one-line C testcase that triggers the same issue:

static int x[57600] = { 0 };

and generated assembler code which the GNU-based as cannot handle:

.zerofill __DATA,__bss6,_x,230400,6
.subsections_via_symbols


[Bug target/61099] Mac 2GB file limit error

2014-05-09 Thread dominiq at lps dot ens.fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61099

Dominique d'Humieres dominiq at lps dot ens.fr changed:

   What|Removed |Added

 Target||*-apple-darwin*
  Component|fortran |target
  Known to work||4.5.0

--- Comment #5 from Dominique d'Humieres dominiq at lps dot ens.fr ---
zerofill has been introduced at r167242 and AFACT is darwin specific.


[Bug target/61099] Mac 2GB file limit error

2014-05-09 Thread barry.j.mcinnes at noaa dot gov
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61099

--- Comment #6 from Barry McInnes barry.j.mcinnes at noaa dot gov ---
Is there any documentation on the arguments -Wa,-q ?
With a link from Macports to /usr/bin/clang one program works without -Wa,-q,
but others still need those parameters to get rid of the zero fill error.


[Bug target/61099] Mac 2GB file limit error

2014-05-09 Thread dominiq at lps dot ens.fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61099

--- Comment #7 from Dominique d'Humieres dominiq at lps dot ens.fr ---
 Is there any documentation on the arguments -Wa,-q ?

-Wa,* is documented somewhere in the manual as the way to tell the assembler to
use the option *. AFAIR 'as -q' is documented (otherwise I won't have guessed
it), but I don't have a pointer.

Note that another workaround is to make the array allocatable.