public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/95456] New: [11 Regression] gcc/gcc.c:6035:16: runtime error: null pointer passed as argument 2, which is declared to never be null
Date: Mon, 01 Jun 2020 08:30:26 +0000	[thread overview]
Message-ID: <bug-95456-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 95456
           Summary: [11 Regression] gcc/gcc.c:6035:16: runtime error: null
                    pointer passed as argument 2, which is declared to
                    never be null
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: driver
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: aoliva at gcc dot gnu.org
            Blocks: 63426
  Target Milestone: ---

Since the Alexander's changes I see:

$ diff --git a/gcc/gcc.c b/gcc/gcc.c
index e2362175f40..44090a8e713 100644
--- a/gcc/gcc.c
+++ b/gcc/gcc.c
@@ -6032,8 +6032,11 @@ do_spec_1 (const char *spec, int inswitch, const char
*soft_matched_part)
                    if (dumpdir_length)
                      memcpy (tmp, dumpdir, dumpdir_length);
                    if (!outbase_length)
+                     {
+                       gcc_assert (input_basename);
                      memcpy (tmp + dumpdir_length, input_basename,
                              basename_length);
+                     }
                    else
                      memcpy (tmp + dumpdir_length, outbase,
                              outbase_length);

$ ./xgcc -B. /tmp/foo.c --save-temps
xgcc: internal compiler error: in do_spec_1, at gcc.c:6036
0x403cea do_spec_1
        /home/marxin/Programming/gcc/gcc/gcc.c:6036
0x4130a1 process_brace_body
        /home/marxin/Programming/gcc/gcc/gcc.c:7122


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
[Bug 63426] [meta-bug] Issues found with -fsanitize=undefined

             reply	other threads:[~2020-06-01  8:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01  8:30 marxin at gcc dot gnu.org [this message]
2020-06-01  8:31 ` [Bug driver/95456] " marxin at gcc dot gnu.org
2020-06-02  7:34 ` rguenth at gcc dot gnu.org
2020-06-02  9:03 ` marxin at gcc dot gnu.org
2020-06-03  5:49 ` marxin at gcc dot gnu.org
2020-06-04  7:40 ` aoliva at gcc dot gnu.org
2020-06-06  1:42 ` cvs-commit at gcc dot gnu.org
2020-06-06  1:54 ` aoliva 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-95456-4@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).