From: Segher Boessenkool <segher@kernel.crashing.org>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: Michael Meissner <meissner@linux.ibm.com>,
Bill Schmidt <wschmidt@linux.ibm.com>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
Jakub Jelinek <jakub@redhat.com>,
Peter Bergner <bergner@linux.ibm.com>,
David Edelsohn <dje.gcc@gmail.com>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: [power-iee128] How to specify linker flags
Date: Mon, 3 Jan 2022 04:34:38 -0600 [thread overview]
Message-ID: <20220103103438.GO614@gate.crashing.org> (raw)
In-Reply-To: <ceeae9c4-32eb-f09d-430a-2e24a3e47b02@netcologne.de>
Hi!
On Mon, Jan 03, 2022 at 11:19:21AM +0100, Thomas Koenig wrote:
> One additional point. The linker does not understand
> -mno-gnu-attribute:
That is a GCC option, not an ld one. If you use it to compile some
file there will be no .gnu.attributes section generated for that
translation unit.
Segher
next prev parent reply other threads:[~2022-01-03 10:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 14:43 [RFC] User-visible changes for powerpc64-le-linux ABI changes Thomas Koenig
2021-11-01 15:54 ` Bill Schmidt
2021-11-01 17:32 ` Thomas Koenig
2021-11-01 17:45 ` Jakub Jelinek
2021-11-02 6:19 ` Thomas Koenig
2021-11-04 4:41 ` Michael Meissner
2021-11-01 18:46 ` Michael Meissner
2021-11-15 20:27 ` Thomas Koenig
2021-11-15 22:14 ` Peter Bergner
2021-11-15 23:42 ` Michael Meissner
2021-11-16 7:51 ` Thomas Koenig
2021-11-19 14:19 ` Jakub Jelinek
2021-11-19 17:30 ` Segher Boessenkool
2021-11-19 19:09 ` Thomas Koenig
2021-11-19 19:36 ` Peter Bergner
2021-11-19 21:30 ` Segher Boessenkool
2022-01-02 22:58 ` [power-iee128] How to specify linker flags Thomas Koenig
2022-01-03 10:19 ` Thomas Koenig
2022-01-03 10:33 ` Jakub Jelinek
2022-01-03 15:23 ` [power-iee128] libgfortran: Use -mno-gnu-attribute in libgfortran Jakub Jelinek
2022-01-03 15:27 ` Thomas Koenig
2022-01-03 10:34 ` Segher Boessenkool [this message]
2022-01-05 21:20 ` [power-iee128] How to specify linker flags Michael Meissner
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=20220103103438.GO614@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=meissner@linux.ibm.com \
--cc=tkoenig@netcologne.de \
--cc=wschmidt@linux.ibm.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).