public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Ian Blanes <ian@lagresca.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/10227: Random segfaults
Date: Sat, 12 Apr 2003 18:26:00 -0000	[thread overview]
Message-ID: <20030412182600.30586.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/10227; it has been noted by GNATS.

From: Ian Blanes <ian@lagresca.org>
To: gcc-gnats@gcc.gnu.org, <gcc-bugs@gcc.gnu.org>, <nobody@gcc.gnu.org>,
   <gcc-prs@gcc.gnu.org>,
   <arbonline@users.sourceforge.net?Subject=Re%3A%20bootstrap%2F10227%3A%20Random%20segfaults&Body=http%3A%2F%2Fgcc.gnu.org%2Fcgi-bin%2Fgnatsweb.pl%3Fcmd%3Dview%2520audit-trail%26database%3Dgcc%26pr%3D10227>
Cc:  
Subject: Re: bootstrap/10227: Random segfaults
Date: Sat, 12 Apr 2003 20:18:07 +0200 (CEST)

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10227
 
 I thnink I haven't broken memory modules as I can compile gcc-3.2.1
 succesfully, this kink of thing only happens with gcc. I can compile
 kernel always.
 
 ian
 


             reply	other threads:[~2003-04-12 18:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-12 18:26 Ian Blanes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-10 14:31 ebotcazou
2003-03-26 19:36 Steven Bosscher
2003-03-26 18:16 arbonline

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=20030412182600.30586.qmail@sources.redhat.com \
    --to=ian@lagresca.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).