From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: gcc-patches@gcc.gnu.org, Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
Ian Lance Taylor <iant@google.com>
Subject: Re: Unreviewed libgcc build patch
Date: Tue, 21 Jun 2011 15:13:00 -0000 [thread overview]
Message-ID: <yddhb7ji7ie.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <BANLkTin+gYodAUbh4R+=6mmYBE1RAb09mw@mail.gmail.com> (Paolo Bonzini's message of "Tue, 21 Jun 2011 16:12:05 +0200")
Paolo Bonzini <bonzini@gnu.org> writes:
> Ok without the commented info evaluation, and with the per-target
> macro renamed to c_flags-$<.
Here's what I've installed after rebuilding libgcc and verifying that
-fexceptions still isn't applied to enable-execute-stack.c.
Thanks.
Rainer
2011-06-21 Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
* shared-object.mk (c_flags-$o): Save c_flags.
($(base)$(objext)): Use it.
($(base)_s$(objext)): Likewise.
Index: libgcc/shared-object.mk
===================================================================
--- libgcc/shared-object.mk (revision 175260)
+++ libgcc/shared-object.mk (working copy)
@@ -6,13 +6,15 @@
base := $(basename $(notdir $o))
+c_flags-$o := $(c_flags)
+
ifeq ($(suffix $o),.c)
$(base)$(objext): $o
- $(gcc_compile) $(c_flags) -c $< $(vis_hide)
+ $(gcc_compile) $(c_flags-$<) -c $< $(vis_hide)
$(base)_s$(objext): $o
- $(gcc_s_compile) $(c_flags) -c $<
+ $(gcc_s_compile) $(c_flags-$<) -c $<
else
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
prev parent reply other threads:[~2011-06-21 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 11:09 Rainer Orth
2011-06-21 15:08 ` Paolo Bonzini
2011-06-21 15:13 ` Rainer Orth [this message]
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=yddhb7ji7ie.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=Ralf.Wildenhues@gmx.de \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.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).