From: Almudena Garcia <liberamenso10000@gmail.com>
To: gcc-patches@gcc.gnu.org,
Thomas Schwinge <thomas@codesourcery.com>,
bug-hurd <bug-hurd@gnu.org>
Subject: Re: [PATCH] Hurd: Enable ifunc by default
Date: Mon, 21 Dec 2020 01:05:29 +0100 [thread overview]
Message-ID: <CA+vQsMhqufVMo4rBU8jALwH+f1aF67tub1DB__smkM2fdhLTuA@mail.gmail.com> (raw)
In-Reply-To: <20201220231052.otcdxcl4zsgcxro2@function>
What do you need exactly? How can we test It?
El lun, 21 dic 2020 a las 0:11, Samuel Thibault (<samuel.thibault@gnu.org>)
escribió:
> Ping?
>
> Samuel Thibault, le dim. 08 nov. 2020 23:52:51 +0100, a ecrit:
> > The binutils bugs seem to have been fixed.
> >
> > 2020-11-08 Samuel Thibault <samuel.thibault@ens-lyon.org>
> >
> > gcc/
> > * config.gcc: Enable default_gnu_indirect_function in *-*-gnu*
> > target (but not *-*-kfreebsd*-gnu | *-*-kopensolaris*-gnu).
> > ---
> > gcc/config.gcc | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/gcc/config.gcc b/gcc/config.gcc
> > index b42ebc4e5be..a347c2cec7c 100644
> > --- a/gcc/config.gcc
> > +++ b/gcc/config.gcc
> > @@ -3538,7 +3538,9 @@ esac
> > case ${target} in
> > *-*-linux*android*|*-*-linux*uclibc*|*-*-linux*musl*)
> > ;;
> > -*-*-linux*)
> > +*-*-kfreebsd*-gnu | *-*-kopensolaris*-gnu)
> > + ;;
> > +*-*-linux* | *-*-gnu*)
> > case ${target} in
> > aarch64*-* | arm*-* | i[34567]86-* | powerpc*-* | s390*-* |
> sparc*-* | x86_64-*)
> > default_gnu_indirect_function=yes
> > --
> > 2.20.1
> >
>
>
next prev parent reply other threads:[~2020-12-21 0:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-08 22:52 Samuel Thibault
2020-11-21 16:42 ` Samuel Thibault
2020-12-04 23:19 ` Samuel Thibault
2020-12-20 23:10 ` Samuel Thibault
2020-12-21 0:05 ` Almudena Garcia [this message]
2020-12-21 0:14 ` Samuel Thibault
2021-01-10 23:59 ` Samuel Thibault
2021-01-13 11:14 ` Thomas Schwinge
2021-01-18 20:05 ` Joseph Myers
2021-01-18 20:25 ` Samuel Thibault
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=CA+vQsMhqufVMo4rBU8jALwH+f1aF67tub1DB__smkM2fdhLTuA@mail.gmail.com \
--to=liberamenso10000@gmail.com \
--cc=bug-hurd@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=thomas@codesourcery.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).