From: Allan Sandfeld Jensen <allan.jensen@qt.io>
To: GCC Patches <gcc-patches@gcc.gnu.org>,
Olivier Hainque <hainque@adacore.com>
Subject: Re: issue with behavior change of gcc -r between gcc-8 and gcc-9
Date: Thu, 02 Apr 2020 10:37:22 +0200 [thread overview]
Message-ID: <4229934.LvFx2qVVIh@twilight> (raw)
In-Reply-To: <4B424DF9-6181-42AE-BB29-86420442E6CA@adacore.com>
On Wednesday, 1 April 2020 19:48:11 CEST Olivier Hainque wrote:
>
> -r 's business was to arrange for the linker not to
> complain because the closure is incomplete, leaving us
> with complete control of the closure.
>
> It doesn't seem to me there was a really strong motivation
> to suddenly have -r influence the closure the way it now does.
>
> Would it be possible to revert to the previous behavior
> and document it ?
>
> Or maybe allow it to be controllable by the target ports ?
>
> Or provide something to bring back the flexibility we had
> if we really believe the default should change ? (I'm not
> convinced)
-r is used for relinking. The idea behind the change was to make it directly
suitable for that. It takes object files and relinks them into a new object
file. It gives the caller complete control.
It sounds like you are missing some way to add startfiles? A reverse of
-nostartfiles?
But hopefully you can just use the linker directly? Unless you have LTO
enabled object files you dont need the compiler to link.
`Allan
next prev parent reply other threads:[~2020-04-02 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 17:48 Olivier Hainque
2020-04-01 20:01 ` Olivier Hainque
2020-04-01 20:42 ` Iain Sandoe
2020-04-01 21:04 ` Olivier Hainque
2020-04-02 8:37 ` Allan Sandfeld Jensen [this message]
2020-04-06 9:47 ` Olivier Hainque
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=4229934.LvFx2qVVIh@twilight \
--to=allan.jensen@qt.io \
--cc=gcc-patches@gcc.gnu.org \
--cc=hainque@adacore.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).