public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikestump at comcast dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/66509] the new clang-based assembler in Xcode 7 on 10.11 fails on the libjava/java/lang/reflect/natArray.cc file from FSF gcc 5.1 at -m32
Date: Thu, 11 Jun 2015 17:15:00 -0000	[thread overview]
Message-ID: <bug-66509-4-CUM8fnkVn0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66509-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66509

--- Comment #12 from Mike Stump <mikestump at comcast dot net> ---
Here is a case where we wish for actual feature testing of all the bits instead
of the coarse grain, are we FSF gas 2.9 or later.  Default should be things
work nicely, and the feature testing should be to identify incomplete or broken
things.  Given the propensity for people to write a test, is this 2.x or later,
that is a direct indication they wrote it wrong in the first place.  Tests
should always be 2.x or earlier to identify broken.


  parent reply	other threads:[~2015-06-11 17:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-66509-4@http.gcc.gnu.org/bugzilla/>
2015-06-11 13:20 ` pinskia at gcc dot gnu.org
2015-06-11 13:28 ` howarth.at.gcc at gmail dot com
2015-06-11 13:30 ` pinskia at gcc dot gnu.org
2015-06-11 13:34 ` iains at gcc dot gnu.org
2015-06-11 13:40 ` pinskia at gcc dot gnu.org
2015-06-11 14:23 ` howarth.at.gcc at gmail dot com
2015-06-11 16:56 ` howarth.at.gcc at gmail dot com
2015-06-11 17:15 ` mikestump at comcast dot net [this message]
2015-06-11 17:50 ` howarth.at.gcc at gmail dot com
2015-06-11 20:08 ` howarth.at.gcc at gmail dot com
2015-06-11 20:53 ` mrs at gcc dot gnu.org
2015-06-11 21:24 ` howarth.at.gcc at gmail dot com
2015-06-11 23:32 ` howarth.at.gcc at gmail dot com
2015-06-26 21:21 ` pinskia at gcc dot gnu.org
2015-06-30  2:11 ` mrs at gcc dot gnu.org
2015-07-01 14:01 ` howarth.at.gcc at gmail dot com
2015-07-01 18:21 ` mrs at gcc dot gnu.org
2015-07-02  1:06 ` howarth.at.gcc at gmail dot com
2015-07-02  7:34 ` mrs at gcc dot gnu.org
2015-07-03 12:57 ` howarth.at.gcc at gmail dot com
2015-07-03 17:01 ` mrs at gcc dot gnu.org
2015-07-03 17:51 ` mrs at gcc dot gnu.org
2015-07-04 12:11 ` howarth.at.gcc at gmail dot com

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-66509-4-CUM8fnkVn0@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).