public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/61099] Mac 2GB file limit error
Date: Wed, 07 May 2014 17:41:00 -0000 [thread overview]
Message-ID: <bug-61099-4-liqcc7CjHv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61099-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61099
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2014-05-07
CC| |iains at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> This sounds like a bug in Apple's assembler.
I think it is: 'as' fails if the bit 32 of the length in '.zerofill' is 1 (bits
above 32 can be set as long as bit 32 is 0).
Workaround: use the Clang 'as', i.e., compile with -Wa,-q.
Note '.zerofill' appeared between r167173 (no zerofill) and r167380 (zerofill).
Note that the code works on darwin10.
This PR should probably closed as INVALID.
next prev parent reply other threads:[~2014-05-07 17:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 15:33 [Bug fortran/61099] New: " barry.j.mcinnes at noaa dot gov
2014-05-07 15:47 ` [Bug fortran/61099] " barry.j.mcinnes at noaa dot gov
2014-05-07 16:31 ` pinskia at gcc dot gnu.org
2014-05-07 16:43 ` barry.j.mcinnes at noaa dot gov
2014-05-07 17:41 ` dominiq at lps dot ens.fr [this message]
2014-05-09 14:29 ` [Bug target/61099] " dominiq at lps dot ens.fr
2014-05-09 15:02 ` barry.j.mcinnes at noaa dot gov
2014-05-09 15:40 ` dominiq at lps dot ens.fr
2014-11-04 0:30 ` fxcoudert at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-61099-4-liqcc7CjHv@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).