From: John Mylchreest <johnm@gentoo.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Olaf Hering <olh@suse.de>,
linux-kernel@vger.kernel.org, stable@kernel.org,
paulus@samba.org
Subject: Re: [PATCH 1/1] POWERPC: Fix ppc32 compile with gcc+SSP in 2.6.16
Date: Sun, 2 Apr 2006 14:56:05 +0100 [thread overview]
Message-ID: <20060402135605.GB3443@getafix.willow.local> (raw)
In-Reply-To: <1143983738.2994.18.camel@laptopd505.fenrus.org>
[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]
On Sun, Apr 02, 2006 at 03:15:38PM +0200, Arjan van de Ven <arjan@infradead.org> wrote:
>
> > Going from that, I can push a patch for gcc upstream to remove the
> > __KERNEL__ dep, but gcc4.1 ships with ssp by standard, and the semantics
> > between the IBM patch for SSP applied to gcc-3 and ggc-4 have changed.
> >
> > -fno-stack-protector would work for gcc4, but for gcc3 it could still be
>
> since this is a thing you have to turn on to get it, not off to not get
> it, I think you're missing something big here ;)
>
> > patially enabled, and requires -fno-stack-protector-all. Mind If I ask
> > whats incorrect about defining __KERNEL__ for the bootcflags?
>
> it's silly and it's a non-standard gcc ... better get the gcc fixed to
> at least have the upstream protocol of having to turn it on not off..
It gets turned on elsewhere (gcc spec), but principle for me is that if its
enabled it still leaks and breaks this code. At the moment (following
from existing patches you put to this list) this mix will break until we
get stack-protector ported.
--
Role: Gentoo Linux Kernel Lead
Gentoo Linux: http://www.gentoo.org
Public Key: gpg --recv-keys 9C745515
Key fingerprint: A0AF F3C8 D699 A05A EC5C 24F7 95AA 241D 9C74 5515
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-04-02 13:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-01 22:48 John Mylchreest
2006-04-02 8:58 ` Olaf Hering
2006-04-02 10:22 ` John Mylchreest
2006-04-02 10:28 ` Olaf Hering
2006-04-02 10:58 ` John Mylchreest
2006-04-02 11:10 ` Olaf Hering
2006-04-02 11:20 ` John Mylchreest
2006-04-02 11:42 ` Olaf Hering
2006-04-04 8:57 ` John Mylchreest
2006-04-04 9:41 ` Olaf Hering
2006-04-04 10:01 ` John Mylchreest
2006-04-04 10:58 ` Olaf Hering
2006-04-10 9:01 ` John Mylchreest
2006-04-02 13:15 ` Arjan van de Ven
2006-04-02 13:56 ` John Mylchreest [this message]
2006-04-02 14:01 ` Olaf Hering
2006-04-02 14:35 ` John Mylchreest
2006-04-02 14:49 ` Arjan van de Ven
2006-04-02 15:22 ` John Mylchreest
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=20060402135605.GB3443@getafix.willow.local \
--to=johnm@gentoo.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
--cc=paulus@samba.org \
--cc=stable@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
all inboxes | Powered by JetHome®