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 target/50077] FAIL: gcc.target/i386/pr49866.c (test for excess errors) on x86_64-apple-darwin10
Date: Thu, 02 Feb 2012 16:06:00 -0000	[thread overview]
Message-ID: <bug-50077-4-EiqNTnjkpW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50077-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-02-02 16:06:05 UTC ---
> clang seems to support -mcmodel=large - at least at 3.1 - so any necessary
> ld64/dyld support is available.

The test compiles (using -c) with

Apple clang version 1.7 (tags/Apple/clang-77) (based on LLVM 2.9svn)

> This is not likely to get fixed in the short term (certainly not in stage 4) -
> so we'll have to decide between XFAIL/tolerate the noise in the error logs.

When XFAILed, this kind of bug disappears from the radar scopes and tends to
rot forever (see pr10901) until it resurfaces in a nasty way. I'ld prefer to
change the summary to something such as "large model is broken on
*86*-apple-darwin*" to point to the real problem.


  parent reply	other threads:[~2012-02-02 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-13 15:42 [Bug target/50077] New: " dominiq at lps dot ens.fr
2012-01-09 21:46 ` [Bug target/50077] " dominiq at lps dot ens.fr
2012-02-02 11:40 ` iains at gcc dot gnu.org
2012-02-02 16:06 ` dominiq at lps dot ens.fr [this message]
2015-01-03 12:45 ` [Bug target/50077] FAIL: gcc.target/i386/pr49866.c (test for excess errors) on x86_64-apple-darwin1* dominiq at lps dot ens.fr

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-50077-4-EiqNTnjkpW@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).