public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/60436] [4.8/4.9 Regression] C preprocessor segfaults on assembly file
Date: Thu, 06 Mar 2014 09:24:00 -0000	[thread overview]
Message-ID: <bug-60436-4-MSN49Czejw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60436-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60436

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Strange, can't reproduce this myself using the same options, neither in
bootstrapped cc1, nor in non-bootstrapped -O0 built, nor bootstrapped cc1 under
valgrind, both 4.8 (older and latest) and trunk.
I'd have thought this would be r200376, but that is fixed on the trunk and now
(since today) on the 4.8 branch too.


  parent reply	other threads:[~2014-03-06  9:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06  2:05 [Bug preprocessor/60436] New: " dan.doel at gmail dot com
2014-03-06  8:30 ` [Bug preprocessor/60436] [4.8/4.9 Regression] " trippels at gcc dot gnu.org
2014-03-06  9:24 ` jakub at gcc dot gnu.org [this message]
2014-03-06 10:29 ` trippels at gcc dot gnu.org
2014-03-06 10:40 ` trippels at gcc dot gnu.org
2014-03-06 14:09 ` trippels at gcc dot gnu.org
2014-03-06 14:31 ` trippels at gcc dot gnu.org
2014-03-06 18:09 ` joseph at codesourcery dot com
2014-03-31  9:31 ` rguenth at gcc dot gnu.org
2014-11-24 12:29 ` [Bug preprocessor/60436] [4.8/4.9/5 " jakub at gcc dot gnu.org
2014-11-25 11:17 ` jakub at gcc dot gnu.org
2014-11-28 13:37 ` jakub at gcc dot gnu.org
2014-11-28 17:06 ` jakub at gcc dot gnu.org
2014-11-28 17:11 ` jakub at gcc dot gnu.org

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-60436-4-MSN49Czejw@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).