From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: Paolo Bonzini <bonzini@gnu.org>,
gcc-patches@gcc.gnu.org,
Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
Mike Stump <mikestump@comcast.net>,
"Loren J. Rittle" <ljrittle@acm.org>,
Kai Tietz <ktietz@redhat.com>,
Dave Korn <dave.korn.cygwin@gmail.com>,
Jason Thorpe <thorpej@netbsd.org>,
Krister Walfridsson <krister.walfridsson@gmail.com>,
Uros Bizjak <ubizjak@gmail.com>,
Richard Henderson <rth@redhat.com>,
Eric Botcazou <ebotcazou@adacore.com>
Subject: Re: [build] Move ENABLE_EXECUTE_STACK to toplevel libgcc
Date: Tue, 07 Jun 2011 19:17:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1106071909020.3034@digraph.polyomino.org.uk> (raw)
In-Reply-To: <yddaadtk6ag.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
On Tue, 7 Jun 2011, Rainer Orth wrote:
> > So my view is that you should define __LIBGCC_TRAMPOLINE_SIZE__, only if
> > -fbuilding-libgcc.
>
> I can give it a try if I can figure out how to define -fbuilding-libgcc
> via the option handling machinery. I just want to avoid having to
That should be no more than
; Define extra predefined macros for use in libgcc.
fbuilding-libgcc
C ObjC C++ ObjC++ Undocumented Var(flag_building_libgcc)
in c.opt.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2011-06-07 19:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 18:09 Rainer Orth
2011-05-30 20:09 ` Kai Tietz
2011-05-31 9:45 ` Paolo Bonzini
2011-05-31 16:40 ` Rainer Orth
2011-05-31 16:57 ` Paolo Bonzini
2011-06-03 15:45 ` Rainer Orth
2011-06-03 16:01 ` Paolo Bonzini
2011-06-06 9:18 ` Rainer Orth
2011-06-06 9:23 ` Paolo Bonzini
2011-06-07 15:20 ` Joseph S. Myers
2011-06-07 15:31 ` Rainer Orth
2011-06-07 15:45 ` Paolo Bonzini
2011-06-07 19:17 ` Joseph S. Myers [this message]
2011-06-09 7:50 ` Rainer Orth
2011-06-09 9:57 ` Joseph S. Myers
2011-06-09 12:06 ` Bernd Schmidt
2011-06-04 11:00 ` Gerald Pfeifer
2011-06-04 11:17 ` Andreas Schwab
2011-06-07 14:00 ` Joseph S. Myers
2011-06-07 14:57 ` Rainer Orth
2011-05-31 18:11 ` Mike Stump
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=Pine.LNX.4.64.1106071909020.3034@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=bonzini@gnu.org \
--cc=dave.korn.cygwin@gmail.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=krister.walfridsson@gmail.com \
--cc=ktietz@redhat.com \
--cc=ljrittle@acm.org \
--cc=mikestump@comcast.net \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=rth@redhat.com \
--cc=thorpej@netbsd.org \
--cc=ubizjak@gmail.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).