public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/61613] ,##__VA_ARGS__ fails to expand the first variadic argument if it is a macro-name
Date: Tue, 12 Aug 2014 13:38:00 -0000	[thread overview]
Message-ID: <bug-61613-4-KXJbAx7pkN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61613-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61613

--- Comment #8 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to David Krauss from comment #6)
> I'd like to take it 100% but the testsuite isn't working on my system. The
> patch is small enough and unobscure enough that it's easier for someone else
> to take responsibility than for me to dedicate another day to GCC build
> configuration.

If you are a sporadic contributor, the easiest and cheapest way to work on GCC
is to get an account in the compile farm: https://gcc.gnu.org/wiki/CompileFarm
and use one of the many scripts in contrib/ (or my own gccfarming script:
https://gcc.gnu.org/wiki/ManuelL%C3%B3pezIb%C3%A1%C3%B1ez?action=AttachFile&do=view&target=gccfarming)
to bootstrap and regression test patches.
>From gcc-bugs-return-458275-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Aug 12 14:11:56 2014
Return-Path: <gcc-bugs-return-458275-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31679 invoked by alias); 12 Aug 2014 14:11:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30518 invoked by uid 48); 12 Aug 2014 14:11:44 -0000
From: "vapier at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/60465] Compiling glibc-2.17,2.18 with gcc-4.8.2 and binutils-2.23.2,2.24 results in segfaults in _start / elf_get_dynamic_info
Date: Tue, 12 Aug 2014 14:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 4.8.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vapier at gentoo dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60465-4-1Ay8x1iL87@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60465-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60465-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-08/txt/msg00772.txt.bz2
Content-length: 196

https://gcc.gnu.org/bugzilla/show_bug.cgi?id`465

--- Comment #9 from Mike Frysinger <vapier at gentoo dot org> ---
i've verified that 4.8.0 & 4.9.1 fail as well :/

binutils 2.24 doesn't help


      parent reply	other threads:[~2014-08-12 13:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-61613-4@http.gcc.gnu.org/bugzilla/>
2014-06-25 19:31 ` arthur.j.odwyer at gmail dot com
2014-06-26 11:41 ` rguenth at gcc dot gnu.org
2014-08-10  9:04 ` potswa at mac dot com
2014-08-11  7:09 ` potswa at mac dot com
2014-08-11 23:50 ` potswa at mac dot com
2014-08-12  0:08 ` arthur.j.odwyer at gmail dot com
2014-08-12 13:38 ` manu at gcc dot gnu.org [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=bug-61613-4-KXJbAx7pkN@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).