From: Alan Modra <amodra@gmail.com>
To: Mike Stump <mikestump@comcast.net>
Cc: Michael Matz <matz@suse.de>,
Segher Boessenkool <segher@kernel.crashing.org>,
Andreas Schwab <schwab@suse.de>,
gcc-patches@gcc.gnu.org
Subject: Re: [RS6000] Don't pass -many to the assembler
Date: Tue, 13 Nov 2018 01:33:00 -0000 [thread overview]
Message-ID: <20181113013255.GF29784@bubble.grove.modra.org> (raw)
In-Reply-To: <627530E2-B6F7-4DF2-A363-A5483A6EEED3@comcast.net>
On Mon, Nov 12, 2018 at 04:34:34PM -0800, Mike Stump wrote:
> On Nov 12, 2018, at 3:13 PM, Alan Modra <amodra@gmail.com> wrote:
> >
> > For people developing new code, it's the right way to go, and
> > especially so for people working on gcc itself. For people just
> > wanting stuff to compile, not so much. I fully expect a chorus of
> > *MORON* or worse to come from the likes of the linux kernel rabble.
>
> So, if you just want to hear people whine...
I'm happy to hear other points of view. Ignore my hyperbole.
> On darwin, we (darwin, as a platform decision) like all instructions available from the assembler.
OK, fair enough. Another option is to just disable -many when gcc is
in development, like we enable checking.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2018-11-13 1:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 11:49 Alan Modra
2018-11-12 13:28 ` Alan Modra
2018-11-12 14:39 ` Michael Matz
2018-11-12 14:52 ` Andreas Schwab
2018-11-12 15:43 ` Segher Boessenkool
2018-11-12 16:17 ` Michael Matz
2018-11-12 23:13 ` Alan Modra
2018-11-13 0:34 ` Mike Stump
2018-11-13 0:41 ` Iain Sandoe
2018-11-13 1:33 ` Alan Modra [this message]
2018-11-13 11:39 ` Segher Boessenkool
2018-11-13 17:49 ` Peter Bergner
2018-11-13 18:07 ` Iain Sandoe
2018-11-13 18:39 ` Peter Bergner
2018-11-26 23:03 ` Mike Stump
2018-11-14 3:14 ` Alan Modra
2018-12-13 10:26 ` Alan Modra
2018-12-13 15:02 ` David Edelsohn
2018-11-12 17:51 ` Peter Bergner
2019-05-21 12:52 Alan Modra
2019-05-21 14:48 ` Segher Boessenkool
2019-05-22 3:26 ` Alan Modra
2019-05-22 20:29 ` Segher Boessenkool
2020-04-06 20:35 ` Sebastian Huber
2020-04-06 22:32 ` Segher Boessenkool
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=20181113013255.GF29784@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=matz@suse.de \
--cc=mikestump@comcast.net \
--cc=schwab@suse.de \
--cc=segher@kernel.crashing.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).