public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/63591] be more strict when accepting parameter forward declarations
Date: Sun, 19 Oct 2014 09:13:00 -0000	[thread overview]
Message-ID: <bug-63591-4-8JVg5kRmaN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63591-4@http.gcc.gnu.org/bugzilla/>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 4610 bytes --]

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

--- Comment #8 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Andreas Schwab from comment #7)
> A function declaration with forward declared parameters it is a prototype,
> sort of.  Not defining the forward declared parameter as a real parameter
> should probably be flagged as an error.

Indeed. Still someone has to implement it... Kjetil?
>From gcc-bugs-return-464443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Oct 19 09:13:00 2014
Return-Path: <gcc-bugs-return-464443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3796 invoked by alias); 19 Oct 2014 09:13:00 -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 3776 invoked by uid 48); 19 Oct 2014 09:12:55 -0000
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63594] New: [5 Regression] ICE: in ix86_vector_duplicate_value, at config/i386/i386.c:39831 with -mavx512f
Date: Sun, 19 Oct 2014 12:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zsojka at seznam dot cz
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter attachments.created
Message-ID: <bug-63594-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: 2014-10/txt/msg01464.txt.bz2
Content-length: 2319

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

            Bug ID: 63594
           Summary: [5 Regression] ICE: in ix86_vector_duplicate_value, at
                    config/i386/i386.c:39831 with -mavx512f
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zsojka at seznam dot cz

Created attachment 33758
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id3758&actioníit
reduced testcase

Compiler output:
$ gcc -mavx512f testcase.c
testcase.c: In function 'foo_1':
testcase.c:6:11: internal compiler error: in ix86_vector_duplicate_value, at
config/i386/i386.c:39831
   __v64qi v1 = {
           ^
0xe76c32 ix86_vector_duplicate_value
        /mnt/svn/gcc-trunk/gcc/config/i386/i386.c:39831
0xe82543 ix86_expand_vector_init_duplicate
        /mnt/svn/gcc-trunk/gcc/config/i386/i386.c:39956
0xec2823 ix86_expand_vector_init(bool, rtx_def*, rtx_def*)
        /mnt/svn/gcc-trunk/gcc/config/i386/i386.c:40739
0x100628d gen_vec_initv64qi(rtx_def*, rtx_def*)
        /mnt/svn/gcc-trunk/gcc/config/i386/sse.md:17488
0x8bcfe6 insn_gen_fn::operator()(rtx_def*, rtx_def*) const
        /mnt/svn/gcc-trunk/gcc/recog.h:308
0x8bcfe6 store_constructor
        /mnt/svn/gcc-trunk/gcc/expr.c:6456
0x8bebc6 expand_constructor
        /mnt/svn/gcc-trunk/gcc/expr.c:7873
0x8a3b0a expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
        /mnt/svn/gcc-trunk/gcc/expr.c:9711
0x8b2e83 store_expr(tree_node*, rtx_def*, int, bool)
        /mnt/svn/gcc-trunk/gcc/expr.c:5341
0x8ba2da expand_assignment(tree_node*, tree_node*, bool)
        /mnt/svn/gcc-trunk/gcc/expr.c:5127
0x7a14d8 expand_gimple_stmt_1
        /mnt/svn/gcc-trunk/gcc/cfgexpand.c:3278
0x7a14d8 expand_gimple_stmt
        /mnt/svn/gcc-trunk/gcc/cfgexpand.c:3374
0x7a6a56 expand_gimple_basic_block
        /mnt/svn/gcc-trunk/gcc/cfgexpand.c:5209
0x7a8b06 execute
        /mnt/svn/gcc-trunk/gcc/cfgexpand.c:5815
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.

Tested revisions:
r216429 - ICE
4_9 r213788 - OK


  parent reply	other threads:[~2014-10-19  8:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-18 21:44 [Bug c/63591] New: No syntax error yielded for semicolons inside a function proto, instead code with memory corruption can be created k.s.matheussen at notam02 dot no
2014-10-18 22:49 ` [Bug c/63591] " pinskia at gcc dot gnu.org
2014-10-18 22:56 ` manu at gcc dot gnu.org
2014-10-18 23:07 ` manu at gcc dot gnu.org
2014-10-18 23:19 ` [Bug c/63591] be more strict when accepting parameter forward declarations manu at gcc dot gnu.org
2014-10-19  6:31 ` schwab@linux-m68k.org
2014-10-19  9:13 ` manu at gcc dot gnu.org [this message]
2014-10-19 16:02 ` jsm28 at gcc dot gnu.org

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-63591-4-8JVg5kRmaN@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).