[Bug c/67276] New: duplicated missing terminating character diagnostic

[Bug c/67276] New: duplicated missing terminating character diagnostic

[manu at gcc dot gnu.org]

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

            Bug ID: 67276
           Summary: duplicated missing terminating character diagnostic
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: manu at gcc dot gnu.org
  Target Milestone: ---

>From gcc.dg/pragma-message.c:

#pragma message "

/home/manuel/test.c:1:17: warning: missing terminating " character
 #pragma message "
                 ^
/home/manuel/test.c:1:9: error: missing terminating " character
 #pragma message "
         ^

It doesn't make sense to give a warning if we are going to give an error
anyway. Moreover, this is a pedwarn, so with -pedantic-errors we get two
errors.

[Bug preprocessor/67276] duplicated missing terminating character diagnostic

[manu at gcc dot gnu.org]

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

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

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|c                           |preprocessor

--- Comment #1 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
This affects also C++ and it seems more like a preprocessor issue.
>From gcc-bugs-return-495196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Aug 19 15:07:50 2015
Return-Path: <gcc-bugs-return-495196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15291 invoked by alias); 19 Aug 2015 15:07:49 -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 15241 invoked by uid 48); 19 Aug 2015 15:07:45 -0000
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67277] New: segfault when passing a missing optional argument to an elemental intrinsic
Date: Wed, 19 Aug 2015 15:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mikael at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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 target_milestone attachments.created
Message-ID: <bug-67277-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-08/txt/msg01338.txt.bz2
Content-length: 976

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

            Bug ID: 67277
           Summary: segfault when passing a missing optional argument to
                    an elemental intrinsic
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: mikael at gcc dot gnu.org
  Target Milestone: ---

Created attachment 36214
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id6214&actioníit
test case

The testcase is the intrinsic variant of generic_31.f90 from pr66929.
It leads to a null pointer dereference at runtime when trying to evaluate
the absent optional argument.
The problem is the same as pr66929, we don't have a procedure interface symbol
for the call, so we don't know that the dummy argument of the intrinsic
procedure is optional, and thus assume that it is always present.