public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: abebeos <lazaridis.com+abebeos@gmail.com>
To: Georg-Johann Lay <avr@gjlay.de>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Denis Chertykov <chertykov@gmail.com>,
	 Senthil Kumar Selvaraj <saaadhu@gcc.gnu.org>
Subject: Re: [PATCH] avr: cc0 to mode_cc conversion
Date: Sun, 13 Dec 2020 23:49:01 +0200	[thread overview]
Message-ID: <CADWdT=w+zOQtB-mL=31R0e=yJZenG6VQ_wvEAUK2qLVGpJoWSw@mail.gmail.com> (raw)
In-Reply-To: <5FD662CF.3080701@gjlay.de>

On Sun, 13 Dec 2020 at 20:51, Georg-Johann Lay <avr@gjlay.de> wrote:

> > (I really tried to follow this
> https://gcc.gnu.org/contribute.html#patches,
> > but my stomach)
> >
> > Hi there all!
> >
> > The attached patch contains a new avr-backend, stripped from cc0.
> >
> > The author is gcc maintainer Snethil Kumar Selvaraj (saaadhu),
>
> Hi, AFAIK Senthil has write-after-approval state.  The only avr
> maintainer, at least according to MAINTAINERS, is still Denis, cf.
>
>
> http://gcc.gnu.org/git/?p=gcc.git;a=blob;f=MAINTAINERS;h=32f8a2b72923b791f9687d6a2d555a1780535078;hb=HEAD#l59
>
> I allowed me CCing them.
>
> > the source can be found here:
> >
> > https://github.com/saaadhu/gcc-avr-cc0/tree/avr-cc0-squashed
> >
> > The gcc/g++ testsuites show zero regressions, tested with:
> >
> > https://github.com/abebeos/avr-gnu
> >
> > and confirmed with another testsetup, see:
> >
> > https://gcc.gnu.org/pipermail/gcc-patches/2020-December/561489.html
> >
> > Some more background information within:
> >
> > https://gcc.gnu.org/pipermail/gcc-patches/2020-December/561668.html
> >
> > and
> >
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729
> >
> > (i have this dark feeling that I did the patch submission wrong...
> pressing
> > Send anyways!)
>

(hey, "between us": where did my real-name came from in your email? I
choosed to appear here with an alias "abebeos" - not that it's difficult to
find my real name, but still, it's my choice...)


>
> Sometimes it's more convenient to have a .diff text file, but I don't
> see anything wrong with your submission.


ok

And what it really nice to
> have hunks defined for "(define_" or "^(define_") in your git diff
> setup.  That way it's easier to track in which entity of the machine
> description a change is located.  Just like when you have a change
> in the middle of a long C function, and the diff chunk spells out
> the C function in which it is located.
>

ok

> diff --git a/gcc/config/avr/avr-dimode.md b/gcc/config/avr/avr-dimode.md
>
[...] - (review)

Thank you for taking the time to review.

The author (currently not available) assessed the work as "semi working":

The (lets say) integrator (me), assessed the work as "good enough" - given
status of the gcc10 avr-backend this should be the prioriity (saving it
from extinction).

Possibly all details should be ignored for now, thus it can be merged.

My process/decision (given circumstances) is to "not touch even whitespace"
in the 0-regression-patch.

So, what remains for me now is to produce a tiny document for the
bounty-backers, and just hope that the folks here finds peace&wisdom to do
the right thing.

Over

a
n
d

Out!

.

  reply	other threads:[~2020-12-13 21:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-13 18:51 Georg-Johann Lay
2020-12-13 21:49 ` abebeos [this message]
2020-12-17  8:45 ` Senthil Kumar Selvaraj
2020-12-17 11:21   ` Segher Boessenkool
2020-12-17 15:07     ` Paul Koning
2020-12-18  9:13       ` Segher Boessenkool
2020-12-18 17:13         ` Georg-Johann Lay
2020-12-18 18:28           ` Segher Boessenkool
2020-12-18 21:38             ` abebeos
2021-01-05 13:54   ` Senthil Kumar Selvaraj
2021-01-05 19:06     ` Paul Koning
  -- strict thread matches above, loose matches on Subject: below --
2020-12-12  4:49 abebeos

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='CADWdT=w+zOQtB-mL=31R0e=yJZenG6VQ_wvEAUK2qLVGpJoWSw@mail.gmail.com' \
    --to=lazaridis.com+abebeos@gmail.com \
    --cc=avr@gjlay.de \
    --cc=chertykov@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=saaadhu@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).