public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/104274] FAIL: gcc.dg/analyzer/pr97029.c (test for excess errors)
Date: Thu, 10 Feb 2022 23:02:14 +0000	[thread overview]
Message-ID: <bug-104274-4-1D2H1CmEcE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104274-4@http.gcc.gnu.org/bugzilla/>

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

David Malcolm <dmalcolm at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2022-02-10
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |ASSIGNED

--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Confirmed (with --target=hppa64-hpux11.3)

pr97029.c.006t.gimple with x86_64 has...

VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV    
void setjmp (struct vj pl)
{
  setjmp (pl);
}
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^


...whereas with  --target=hppa64-hpux11.3 has:
VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV    
void setjmp (struct vj pl)
{
  struct vj pl.0;

  setjmp (pl.0);
}
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

It still happens if I rename the function from "setjmp" to "foo".
It no longer happens if I add a dummy field to the struct.

The temporary "pl.0" is created on hppa by:
#4  0x0000000000aa7b3a in gimplify_parameters
(cleanup=cleanup@entry=0x7fffffffd9b0) at ../../src/gcc/function.cc:3939
3926              tree type = TREE_TYPE (data.arg.type);
3927              function_arg_info orig_arg (type, data.arg.named);
3928              if (reference_callee_copied (&all.args_so_far_v, orig_arg))
3929                {
3930                  tree local, t;
3931    
3932                  /* For constant-sized objects, this is trivial; for
3933                     variable-sized objects, we have to play games.  */
3934                  if (TREE_CODE (DECL_SIZE_UNIT (parm)) == INTEGER_CST
3935                      && !(flag_stack_check == GENERIC_STACK_CHECK
3936                           && compare_tree_int (DECL_SIZE_UNIT (parm),
3937                                                STACK_CHECK_MAX_VAR_SIZE) >
0))
3938                    {
3939                      local = create_tmp_var (type, get_name (parm));
3940                      DECL_IGNORED_P (local) = 0;
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

and never assigned to.

  reply	other threads:[~2022-02-10 23:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 18:57 [Bug analyzer/104274] New: " danglin at gcc dot gnu.org
2022-02-10 23:02 ` dmalcolm at gcc dot gnu.org [this message]
2022-02-10 23:38 ` [Bug analyzer/104274] " dmalcolm at gcc dot gnu.org
2022-02-10 23:50 ` dmalcolm at gcc dot gnu.org
2022-02-10 23:59 ` dmalcolm at gcc dot gnu.org
2022-02-11 13:47 ` cvs-commit at gcc dot gnu.org
2022-02-11 13:53 ` dmalcolm 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-104274-4-1D2H1CmEcE@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).