From: Alan Modra <amodra@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [RS6000] Implement -mno-pltseq
Date: Thu, 10 Jan 2019 12:05:00 -0000 [thread overview]
Message-ID: <20190110120457.GR3170@bubble.grove.modra.org> (raw)
In-Reply-To: <20190110110906.GW14180@gate.crashing.org>
On Thu, Jan 10, 2019 at 05:09:06AM -0600, Segher Boessenkool wrote:
> On Mon, Jan 07, 2019 at 12:54:02PM +1030, Alan Modra wrote:
> > Since the last patch untangled inline PLT and TLS marker support there
> > now isn't a way of requesting the older long call sequences on a
> > compiler built with inline PLT support. This patch adds support for
> > a new -mno-pltseq option.
>
> Is this a useful option to have?
I figure the most use it will get is by gcc maintainers and others
investigating bug reports. You get a bug report and can't reproduce
the failure even though compiler flags and gcc version are well
specified. -mno-pltseq gives you a way of quickly trying out
something that might be different in their auto-host.h to yours.
> It needs documentation (in the manual), then.
OK, will do.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2019-01-10 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 1:58 [RS6000] Emit inline PLT when -mno-tls-markers Alan Modra
2019-01-07 2:24 ` [RS6000] Implement -mno-pltseq Alan Modra
2019-01-10 11:09 ` Segher Boessenkool
2019-01-10 12:05 ` Alan Modra [this message]
2019-01-10 11:06 ` [RS6000] Emit inline PLT when -mno-tls-markers 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=20190110120457.GR3170@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).