public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xerofoify at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/94217] [10 Regression] ICE in ipa_find_agg_cst_for_param, at ipa-prop.c:3467 since r10-7237-g4e3d3e40726e1b68
Date: Wed, 18 Mar 2020 18:30:05 +0000	[thread overview]
Message-ID: <bug-94217-4-jTJBuxxEZe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94217-4@http.gcc.gnu.org/bugzilla/>

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

Nicholas Krause <xerofoify at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xerofoify at gmail dot com

--- Comment #1 from Nicholas Krause <xerofoify at gmail dot com> ---
Hi Marin,
I've not sure if this is correct but it does not ICE with this fix:
                tree off = fold_convert (ptr_type_node, op1);
-                   return build_fold_addr_expr_loc
-                       (loc,
+                   return build1_loc
+                       (loc, ADDR_EXPR, TREE_TYPE (op0),
                         fold_build2 (MEM_REF,
                                      TREE_TYPE (TREE_TYPE (op0)),
                                      unshare_expr (op0), off));

should actually be:  
(EXPR_LOCATION(off), ADDR_EXPR, TREE_TYPE (op0),
                         fold_build2 (MEM_REF,
                                      TREE_TYPE (TREE_TYPE (op0)),
                                      unshare_expr (op0), off));

I've tested with your file and I get:
star.ii: In member function ‘int B< <template-parameter-1-1>,
<template-parameter-1-2>, <template-parameter-1-3>, <template-parameter-1-4>,
<template-parameter-1-5> >::_S_key()’:
star.ii:9:19: warning: no return statement in function returning non-void
[-Wreturn-type]
    9 |   int _S_key() {  }
      |                   ^
star.ii: In member function ‘int B< <template-parameter-1-1>,
<template-parameter-1-2>, <template-parameter-1-3>, <template-parameter-1-4>,
<template-parameter-1-5> >::_M_insert_(int*, int*, _Arg&&, _NodeGen&)’:
star.ii:24:1: warning: no return statement in function returning non-void
[-Wreturn-type]
   24 | }


However this seems to be on multiple ade package files so can you test it
against that as well.

  parent reply	other threads:[~2020-03-18 18:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 17:45 [Bug ipa/94217] New: " marxin at gcc dot gnu.org
2020-03-18 17:45 ` [Bug ipa/94217] " marxin at gcc dot gnu.org
2020-03-18 18:30 ` xerofoify at gmail dot com [this message]
2020-03-18 18:43 ` mpolacek at gcc dot gnu.org
2020-03-18 18:51 ` xerofoify at gmail dot com
2020-03-18 19:22 ` marxin at gcc dot gnu.org
2020-03-18 19:37 ` marxin at gcc dot gnu.org
2020-03-19  6:40 ` rguenth at gcc dot gnu.org
2020-03-19  7:43 ` rguenth at gcc dot gnu.org
2020-03-19  9:20 ` cvs-commit at gcc dot gnu.org
2020-03-19  9:20 ` rguenth at gcc dot gnu.org
2020-03-20 11:56 ` tnfchris at gcc dot gnu.org
2020-03-20 12:05 ` tnfchris at gcc dot gnu.org
2020-03-20 16:21 ` tnfchris at gcc dot gnu.org
2020-03-20 16:25 ` marxin at gcc dot gnu.org
2020-03-20 17:28 ` tnfchris 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-94217-4-jTJBuxxEZe@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).