public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jan.echternach at de dot gbs.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/41517] Unexpected behaviour of #pragma in statement context
Date: Thu, 08 Oct 2015 15:21:00 -0000	[thread overview]
Message-ID: <bug-41517-4-WaSPicksAG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-41517-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41517

Jan Echternach <jan.echternach at de dot gbs.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jan.echternach at de dot gbs.com

--- Comment #1 from Jan Echternach <jan.echternach at de dot gbs.com> ---
I can confirm this bug in gcc 4.9 (Debian 4.9.2-10). A different example which
also produces wrong code (should return 0, but returns 1):

//#include <stdio.h>
int main ()
{
    if (0)
#pragma GCC diagnostic ignored "-Wtype-limits"
    {
        //printf ("bug\n");
        return 1;
    }
    //printf ("ok\n");
    return 0;
}

And an example that fails to compile ("error: ‘else’ without a previous ‘if’"):

void foo (void)
{
    if (0)
#pragma GCC diagnostic ignored "-Wtype-limits"
    {}
    else {}
}
>From gcc-bugs-return-499038-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Oct 08 15:37:22 2015
Return-Path: <gcc-bugs-return-499038-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90421 invoked by alias); 8 Oct 2015 15:37:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 90315 invoked by uid 48); 8 Oct 2015 15:37:17 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/67794] [6 regression] internal compiler error: Segmentation fault
Date: Thu, 08 Oct 2015 15:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jamborm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-67794-4-QuD6ndhVjS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67794-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67794-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-10/txt/msg00593.txt.bz2
Content-length: 221

https://gcc.gnu.org/bugzilla/show_bug.cgi?idg794

--- Comment #7 from Martin Jambor <jamborm at gcc dot gnu.org> ---
I have proposed a fix on the mailing list:

https://gcc.gnu.org/ml/gcc-patches/2015-10/msg00858.html


           reply	other threads:[~2015-10-08 15:21 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-41517-4@http.gcc.gnu.org/bugzilla/>]

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=bug-41517-4-WaSPicksAG@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).