From: Richard Sandiford <rdsandiford@googlemail.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Prevent inlining of weak hidden symbols.
Date: Fri, 09 Jul 2010 16:29:00 -0000 [thread overview]
Message-ID: <AANLkTilUBB6lRSME69RFRVgadKrWywQ5expsFSgINxBO@mail.gmail.com> (raw)
In-Reply-To: <AANLkTilF6KQS-mv6vcR9GOvwkKXd3anDRn2QS54Uqb0l@mail.gmail.com>
Um, sorry for the duplication, not used to using the gmail web interface.
I hope it was worth reading twice...
Richard
next prev parent reply other threads:[~2010-07-09 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 16:27 Richard Sandiford
2010-07-09 16:29 ` Richard Sandiford [this message]
2010-07-09 16:32 ` Richard Guenther
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=AANLkTilUBB6lRSME69RFRVgadKrWywQ5expsFSgINxBO@mail.gmail.com \
--to=rdsandiford@googlemail.com \
--cc=gcc-patches@gcc.gnu.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).