public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: preprocessor/8055: CPP0 segfault on FreeBSD + PATCH Date: Fri, 27 Sep 2002 13:56:00 -0000 [thread overview] Message-ID: <20020927205603.13376.qmail@sources.redhat.com> (raw) The following reply was made to PR preprocessor/8055; it has been noted by GNATS. From: Mark Mitchell <mark@codesourcery.com> To: Zack Weinberg <zack@codesourcery.com>, "ak03@gte.com" <ak03@gte.com>, Neil Booth <neil@daikokuya.co.uk> Cc: "gcc-gnats@gcc.gnu.org" <gcc-gnats@gcc.gnu.org>, "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org> Subject: Re: preprocessor/8055: CPP0 segfault on FreeBSD + PATCH Date: Fri, 27 Sep 2002 13:50:20 -0700 --On Friday, September 27, 2002 12:50:09 PM -0700 Zack Weinberg <zack@codesourcery.com> wrote: > Thank you for this bug report. I've reproduced the problem, and > confirm your analysis. I'm going to do a complete bootstrap+test > cycle on a slight modification of your patch (see below) and will > apply to mainline if successful. I think we need to figure out if this is a regression before applying it to the branch. Just in case. If it is a regression, it's fine. Thanks, -- Mark Mitchell mark@codesourcery.com CodeSourcery, LLC http://www.codesourcery.com
next reply other threads:[~2002-09-27 20:56 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-27 13:56 Mark Mitchell [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-04 11:46 Neil Booth 2002-09-27 15:56 Mark Mitchell 2002-09-27 15:16 Zack Weinberg 2002-09-27 13:16 Alexander Kabaev 2002-09-27 12:56 Zack Weinberg 2002-09-26 8:26 ak03
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=20020927205603.13376.qmail@sources.redhat.com \ --to=mark@codesourcery.com \ --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: linkBe 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).