public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/104655] [12 Regression] array subscript 0 is outside array bounds of
Date: Wed, 23 Feb 2022 12:04:38 +0000	[thread overview]
Message-ID: <bug-104655-4-XemuoaMMd9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104655-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Paul Menzel from comment #5)
> Created attachment 52498 [details]
> Preprocessed file `build/bootblock/cpu/x86/lapic/lapic.i` with `-save-temps`
> 
> Sorry for not sharing the file in the first place. First for the coreboot
> case:

This case is a dup of bug 99578.
lapicid:
 uint32_t lapicid = lapic_read(0x020);

static inline __attribute__((always_inline)) uint32_t lapic_read(unsigned int
reg)
{
 if (is_x2apic_mode())
  return x2apic_read(reg);
 else
  return xapic_read(reg);
}

static inline __attribute__((always_inline)) uint32_t xapic_read(unsigned int
reg)
{
 return read32((volatile void *)(uintptr_t)(0xfee00000 + reg));
}

static inline __attribute__((always_inline)) uint32_t read32(const volatile
void *addr)
{
 return *((volatile uint32_t *)(addr));
}

  parent reply	other threads:[~2022-02-23 12:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23  8:12 [Bug tree-optimization/104655] New: " pmenzel+gcc at molgen dot mpg.de
2022-02-23  8:17 ` [Bug tree-optimization/104655] " pinskia at gcc dot gnu.org
2022-02-23 10:39 ` pinskia at gcc dot gnu.org
2022-02-23 10:42 ` rguenth at gcc dot gnu.org
2022-02-23 10:49 ` pmenzel+gcc at molgen dot mpg.de
2022-02-23 10:53 ` jakub at gcc dot gnu.org
2022-02-23 11:14 ` pmenzel+gcc at molgen dot mpg.de
2022-02-23 12:04 ` pinskia at gcc dot gnu.org [this message]
2022-02-23 12:10 ` pmenzel+gcc at molgen dot mpg.de
2022-02-23 17:55 ` msebor 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-104655-4-XemuoaMMd9@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).