public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: "Herman, Andrei" <Andrei_Herman@codesourcery.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH GCC]Add 'force-dwarf-lexical-blocks' command line option
Date: Thu, 08 May 2014 17:26:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1405081725290.4990@digraph.polyomino.org.uk> (raw)
In-Reply-To: <FEC4CADEDABC9E40A1EC17465AAC8402AE41D351@EU-MBX-04.mgc.mentorg.com>

On Thu, 8 May 2014, Herman, Andrei wrote:

> The changes in gcc/c/c-decl.c  are meant to deal with this problem. Declarations
> that would fall into the scope of a newly created label scope are moved into the 
> enclosing "normal" (non label) scope, where they actually belong.

Shouldn't you be able to do something like that for the other cases as 
well, to avoid forcing C99 scoping rules?

In any case, I think you need to run the complete "gcc" testsuite with 
this option enabled and compare with the results for a default testsuite 
run.

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2014-05-08 17:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07  9:32 Herman, Andrei
2014-05-07  9:36 ` pinskia
2014-05-07  9:43   ` Herman, Andrei
2014-05-07 15:59 ` Mike Stump
2014-05-07 17:19   ` Herman, Andrei
2014-05-07 17:25     ` Andrew Pinski
2014-05-07 18:01     ` Mike Stump
2014-05-07 18:01 ` Joseph S. Myers
2014-05-08 14:57   ` Herman, Andrei
2014-05-08 17:26     ` Joseph S. Myers [this message]
2014-05-08 17:44       ` Herman, Andrei
2014-05-08 21:01         ` Joseph S. Myers
2014-06-01 10:33 Herman, Andrei
2014-06-19 21:09 ` Joseph S. Myers
2014-06-21 17:06   ` Herman, Andrei
2014-07-28 13:50   ` Herman, Andrei
2014-08-14 21:14     ` Joseph S. Myers

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=Pine.LNX.4.64.1405081725290.4990@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=Andrei_Herman@codesourcery.com \
    --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).