From: Jeff Law <law@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v2] libgcc: Use braces instead of macro's empty body to avoid xgcc warnings.
Date: Wed, 15 Apr 2015 15:29:00 -0000 [thread overview]
Message-ID: <552E83D1.70005@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
This patch was originally from Chen Gang S. However, his address at
sunrus.com.cn bounces. So presumably he didn't get the approved
message. I'm checking in the patch for him (with the fixed ChangeLog).
I've verified by hand that the warning goes away with a cross toolchain
and that it doesn't affect x86_64-unknown-linux-gnu.
[-- Attachment #2: Re: [PATCH v2] libgcc: Use braces instead of macro's empty body to.eml --]
[-- Type: application/x-message-display, Size: 2546 bytes --]
next reply other threads:[~2015-04-15 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 15:29 Jeff Law [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-01-31 11:33 Chen Gang S
2015-01-31 12:34 ` Andreas Schwab
2015-01-31 14:50 ` Chen Gang S
2015-01-31 15:45 ` Prathamesh Kulkarni
2015-01-31 15:45 ` Marek Polacek
2015-01-31 19:51 ` Chen Gang S
2015-04-14 5:30 ` Jeff Law
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=552E83D1.70005@redhat.com \
--to=law@redhat.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).