From: Joseph Myers <joseph@codesourcery.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH 1/2] Build divdi3 only for architecture that required it
Date: Wed, 10 May 2017 13:24:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1705101321180.3001@digraph.polyomino.org.uk> (raw)
In-Reply-To: <0ef59b2d-8f19-8646-a773-565dd14704f4@linaro.org>
On Wed, 19 Apr 2017, Adhemerval Zanella wrote:
> Now to actually fix it I can think of two possible solutions:
>
> 1. Add divdi3 build on sparc32 as before the patch.
> 2. Enforce -Wl,-noexecstack on ld.so build.
3. Add .note.GNU-stack section in libgcc/config/sparc/lb1spc.S (possibly
conditioned on defined(__ELF__) && defined(__linux__), as in other
architecture-specific .S files). That seems to me to be the right
approach, and would fix it for other software using these libgcc functions
as well. And as a very small safe patch it should be suitable for
backporting onto active GCC release branches.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-05-10 13:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 13:43 Adhemerval Zanella
2017-03-16 13:43 ` [PATCH 2/2] sparc: Fix .udiv plt on libc Adhemerval Zanella
2017-03-16 14:45 ` Florian Weimer
2017-03-16 16:59 ` Adhemerval Zanella
2017-03-27 15:33 ` Adhemerval Zanella
2017-03-16 13:58 ` [PATCH 1/2] Build divdi3 only for architecture that required it Andreas Schwab
2017-03-16 17:00 ` Adhemerval Zanella
[not found] ` <af83ffde-83d3-d7d1-d45e-7c379b7e7123@linaro.org>
2017-04-06 16:11 ` Adhemerval Zanella
2017-04-18 21:21 ` Joseph Myers
2017-04-18 22:29 ` Adhemerval Zanella
2017-04-19 21:01 ` Adhemerval Zanella
2017-05-10 13:24 ` Joseph Myers [this message]
2017-05-10 20:24 ` Adhemerval Zanella
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.20.1705101321180.3001@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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).