From: Joseph Myers <joseph@codesourcery.com>
To: Allan Sandfeld Jensen <linux@carewolf.com>
Cc: <gcc-patches@gcc.gnu.org>, Iain Sandoe <iain@sandoe.co.uk>
Subject: Re: [Patch][GCC] Document and fix -r (partial linking)
Date: Thu, 20 Sep 2018 20:02:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1809201938250.17228@digraph.polyomino.org.uk> (raw)
In-Reply-To: <5399704.KElGaqSPkd@twilight>
On Sat, 1 Sep 2018, Allan Sandfeld Jensen wrote:
> On Montag, 27. August 2018 15:37:15 CEST Joseph Myers wrote:
> > On Sun, 26 Aug 2018, Allan Sandfeld Jensen wrote:
> > > Patch updated. I specifically edited a number of the existing tests that
> > > used both -r and -nostdlib and removed -nostdlib so the patch is
> > > exercised by existing tests. The patch bootstrapped, I didn't notice any
> > > relevant failures when running the test suite (though I could have missed
> > > something, I am never comfortable reading that output).
> >
> > Note that Iain's comments also included that the patch is incomplete
> > because of more specs in gcc.c (VTABLE_VERIFICATION_SPEC,
> > SANITIZER_EARLY_SPEC, SANITIZER_SPEC) that needs corresponding updates to
> > handle -r like -nostdlib.
>
> Updated (but tests not rerun)
Thanks, I've now committed the patch.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-09-20 19:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 16:14 Allan Sandfeld Jensen
2018-08-01 16:32 ` Joseph Myers
2018-08-01 17:12 ` Allan Sandfeld Jensen
2018-08-03 11:56 ` Allan Sandfeld Jensen
2018-08-03 13:27 ` Iain Sandoe
2018-08-11 9:05 ` Allan Sandfeld Jensen
2018-08-20 22:39 ` Joseph Myers
2018-08-23 7:47 ` Iain Sandoe
2018-08-23 21:24 ` Joseph Myers
2018-08-26 18:17 ` Allan Sandfeld Jensen
2018-08-27 13:37 ` Joseph Myers
2018-09-01 10:57 ` Allan Sandfeld Jensen
2018-09-01 11:05 ` Allan Sandfeld Jensen
2018-09-20 20:02 ` Joseph Myers [this message]
2018-08-26 10:34 ` Allan Sandfeld Jensen
2018-08-01 16:39 ` Rainer Orth
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=alpine.DEB.2.21.1809201938250.17228@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
--cc=linux@carewolf.com \
/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).