From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Baruch Burstein <bmburstein@gmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Request easy bug fix
Date: Tue, 15 Feb 2022 12:55:12 +0000 [thread overview]
Message-ID: <CAH6eHdR8vwACqm6gMhD2ay++xsD+J_ru+280h7EVc+mr6+q1uQ@mail.gmail.com> (raw)
In-Reply-To: <CA+34VNK9Z2yCb_gbsLUTgH6m6vo2uT=9Qo-_u_Fo1Ed8Kfow+A@mail.gmail.com>
On Tue, 15 Feb 2022 at 12:34, Baruch Burstein via Gcc <gcc@gcc.gnu.org>
wrote:
> Hi,
>
> I hope it is not inappropriate to call attention to a specific bug.
> https://gcc.gnu.org/bugzilla//show_bug.cgi?id=85487.
> I tried to do it myself, but got lost on the part where I needed to
> compile gcc 3 times and compare test results to some (un)known test
> results.
You compare the test results of your patched gcc to the test results of an
unpatched gcc.
How did you get lost? To "compile gcc 3 times" you just run "make", and it
does that automatically (unless you configured with --disable-bootstrap, in
which case it just compiles once).
> It was too much time and setup for a fix that will probably
> take 2 minutes to implement, so I am asking if someone that already
> contributes to gcc can please look at this. I think it should only
> take a couple of minutes to implement.
>
No change ever takes two minutes, because you have to write tests at a
minimum.
next prev parent reply other threads:[~2022-02-15 12:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 12:33 Baruch Burstein
2022-02-15 12:55 ` Jonathan Wakely [this message]
2022-02-15 13:58 ` David Malcolm
2022-02-15 15:20 ` Jonathan Wakely
[not found] ` <CA+34VNKHGGJAD8BX4COBKrb5H-_pPm2s0ZHwMStVJqmNjTPVig@mail.gmail.com>
2022-10-30 15:01 ` Fwd: " Baruch Burstein
2022-10-31 14:03 ` Jonathan Wakely
2022-10-31 14:23 ` Baruch Burstein
2022-11-01 18:39 ` Fwd: " Jeff Law
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=CAH6eHdR8vwACqm6gMhD2ay++xsD+J_ru+280h7EVc+mr6+q1uQ@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=bmburstein@gmail.com \
--cc=gcc@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).