public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/115009] [15 regression] AVR: ICE in alloc, at value-range-storage.cc:598
Date: Thu, 09 May 2024 21:47:49 +0000	[thread overview]
Message-ID: <bug-115009-4-EKpAzR0DwG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115009-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
(In reply to Jeffrey A. Law from comment #8)
> And on msp430-elf we're getting a codegen correctness issue on msp430-elf. 
> gcc.dg/pr66444.c fails in the simulator.  The -O2 code difference looks like:
> 
> *** good.s      Thu May  9 20:41:37 2024
> --- bad.s       Thu May  9 20:41:44 2024
> *************** baz:
> *** 73,81 ****
>   ; saved regs:(none)
>         ; start of prologue
>         ; end of prologue
> !       MOV.W   #2062, R12
>         CALL    #fn1
> !       MOV.W   #2062, R12
>         CALL    #fn2
>         MOV.B   #0, R12
>         ; start of epilogue
> --- 73,81 ----
>   ; saved regs:(none)
>         ; start of prologue
>         ; end of prologue
> !       MOV.B   #0, R12
>         CALL    #fn1
> !       MOV.B   #0, R12
>         CALL    #fn2
>         MOV.B   #0, R12
>         ; start of epilogue
> 
> 
> We're mucking up the pointer that baz() passes down to fn1 and fn2 I think.

Hmmm, this may be something different.  I can look at it tomorrow.

  parent reply	other threads:[~2024-05-09 21:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09 11:45 [Bug c/115009] New: " manuel.lauss at googlemail dot com
2024-05-09 15:01 ` [Bug tree-optimization/115009] " pinskia at gcc dot gnu.org
2024-05-09 17:06 ` pinskia at gcc dot gnu.org
2024-05-09 17:14 ` pinskia at gcc dot gnu.org
2024-05-09 17:18 ` pinskia at gcc dot gnu.org
2024-05-09 20:07 ` pinskia at gcc dot gnu.org
2024-05-09 20:30 ` law at gcc dot gnu.org
2024-05-09 20:33 ` pinskia at gcc dot gnu.org
2024-05-09 20:36 ` pinskia at gcc dot gnu.org
2024-05-09 20:44 ` law at gcc dot gnu.org
2024-05-09 21:44 ` aldyh at gcc dot gnu.org
2024-05-09 21:46 ` aldyh at gcc dot gnu.org
2024-05-09 21:47 ` aldyh at gcc dot gnu.org [this message]
2024-05-09 21:52 ` pinskia at gcc dot gnu.org
2024-05-10  7:01 ` cvs-commit at gcc dot gnu.org
2024-05-10  7:05 ` aldyh 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-115009-4-EKpAzR0DwG@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).