public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: "Uecker, Martin" <Martin.Uecker@med.uni-goettingen.de>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] mixing of labels and code in C2X
Date: Fri, 6 Nov 2020 22:44:12 +0000	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2011062242550.888692@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1604701525.16603.7.camel@med.uni-goettingen.de>

On Fri, 6 Nov 2020, Uecker, Martin wrote:

> Am Freitag, den 06.11.2020, 22:07 +0000 schrieb Joseph Myers:
> > On Fri, 6 Nov 2020, Uecker, Martin wrote:
> > 
> > > Hi Joseph,
> > > 
> > > here is the revised patch. I remove the 'fallthrough'
> > > code as suggested, so everything becomes even simpler.
> > > Some tests had to be changed then, but it seems Ok to
> > > me.
> > 
> > This patch is missing the new tests.
> > 
> > > +	* gcc.dg/c11-labels-1.c: New test.
> > > +	* gcc.dg/c11-labels-2.c: New test.
> > > +	* gcc.dg/c11-labels-3.c: New test.
> > > +	* gcc.dg/c2x-labels-1.c: New test.
> > > +	* gcc.dg/c2x-labels-2.c: New test.
> > > +	* gcc.dg/c2x-labels-3.c: New test.
> 
> My bad. Here there are.

Thanks.  This version is OK (note that ChangeLog entries now need to be 
included in the commit message, not as changes to the ChangeLog files, and 
the nightly cron job will update the ChangeLog files).

-- 
Joseph S. Myers
joseph@codesourcery.com

      reply	other threads:[~2020-11-06 22:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-13 11:20 Uecker, Martin
2020-09-14 20:30 ` Joseph Myers
2020-11-01 22:34   ` Uecker, Martin
2020-11-02 21:16     ` Joseph Myers
2020-11-06  6:56       ` Uecker, Martin
2020-11-06 22:07         ` Joseph Myers
2020-11-06 22:25           ` Uecker, Martin
2020-11-06 22:44             ` Joseph Myers [this message]

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=alpine.DEB.2.22.394.2011062242550.888692@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=Martin.Uecker@med.uni-goettingen.de \
    --cc=gcc-patches@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).