public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/53496] gcc segfaults when compiling glic
Date: Sat, 26 May 2012 19:22:00 -0000 [thread overview]
Message-ID: <bug-53496-4-vASiDlnCkR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53496-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53496
Mikael Pettersson <mikpe at it dot uu.se> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikpe at it dot uu.se
--- Comment #3 from Mikael Pettersson <mikpe at it dot uu.se> 2012-05-26 18:46:02 UTC ---
(In reply to comment #2)
> Created attachment 27503 [details]
> source of param.c
That file still includes stuff. Please provide the _pre-processed_ file.
next prev parent reply other threads:[~2012-05-26 18:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-26 17:20 [Bug c/53496] New: " justas.poderys at gmail dot com
2012-05-26 17:21 ` [Bug middle-end/53496] " pinskia at gcc dot gnu.org
2012-05-26 17:30 ` justas.poderys at gmail dot com
2012-05-26 19:22 ` mikpe at it dot uu.se [this message]
2012-05-29 10:27 ` rguenth at gcc dot gnu.org
2012-05-29 10:57 ` [Bug middle-end/53496] gcc segfaults when compiling glib redi at gcc dot gnu.org
2013-11-10 19:49 ` pinskia 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-53496-4-vASiDlnCkR@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).