From: Mike Frysinger <vapier@gentoo.org>
To: linux-sh@vger.kernel.org
Subject: Re: stack usage with libgcc math funcs
Date: Thu, 25 Dec 2008 00:15:22 +0000 [thread overview]
Message-ID: <200812241959.56191.vapier@gentoo.org> (raw)
In-Reply-To: <200812241257.33701.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
On Wednesday 24 December 2008 17:57:53 Kaz Kojima wrote:
> Mike Frysinger <vapier@gentoo.org> wrote:
> > i dont know superh assembly, so i cant really check the code myself.
> > starting with at gcc-4.1.2 (at least, gcc-3.4.6 doesnt seem to have this
> > issue), a few objects in libgcc.a lack GNU-stack markings. here is the
> > scanelf output against libgcc.a from gcc-4.3.2. basically, '!WX' just
> > means that the objects do not have a .note.GNU-stack section.
> > assuming libgcc doesnt actually use the stack to exec code, the attached
> > patch should fix things i think.
>
> Thanks for pointing this out.
i'm guessing that means they're correct :)
> Could you please send your
> patches to gcc-patches or file this issue to gcc bugzilla?
i dont think people like it when i post patches to bugzilla. they tell me to
use gcc-patches.
> Unfortunately, now gcc trunk is in stage 4 and any patches
> for non strict regressions can't be accepted temporary.
> I'll schedule these patches for 4.5, then apply them to
> the open branches after 4.5.
well, i would say this is a long standing regression. gcc-3.4.6 does not
result in exec stacks with any of the libgcc.a math functions ... but you're
the gcc expert.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2008-12-25 0:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 17:13 stack usage with libgcc math funcs Mike Frysinger
2008-12-24 17:28 ` Mike Frysinger
2008-12-24 22:57 ` Kaz Kojima
2008-12-25 0:15 ` Mike Frysinger [this message]
2008-12-25 1:22 ` Kaz Kojima
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=200812241959.56191.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=linux-sh@vger.kernel.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