public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/29709] Segmentation fault of cc1.
Date: Sat, 04 Nov 2006 09:59:00 -0000	[thread overview]
Message-ID: <20061104095905.4203.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29709-7155@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from pinskia at gcc dot gnu dot org  2006-11-04 09:59 -------
(In reply to comment #4)
> I tgink if i post there, they will be redirect here :-) [i am wrong on this ?]

but since you are using their modifed source, it might be hard to reproduce
with an FSF GCC which is why you should always post it to where you got the
source first.


-- 


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


  parent reply	other threads:[~2006-11-04  9:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-04  9:42 [Bug c/29709] New: " rezso at rdsor dot ro
2006-11-04  9:43 ` [Bug c/29709] " rezso at rdsor dot ro
2006-11-04  9:48 ` rezso at rdsor dot ro
2006-11-04  9:51 ` [Bug target/29709] " pinskia at gcc dot gnu dot org
2006-11-04  9:54 ` rezso at rdsor dot ro
2006-11-04  9:56 ` rezso at rdsor dot ro
2006-11-04  9:59 ` pinskia at gcc dot gnu dot org [this message]
2006-11-04 11:36 ` rezso at rdsor dot ro

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=20061104095905.4203.qmail@sourceware.org \
    --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).