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 target/103676] [10/11/12 Regression] internal compiler error: in extract_constrain_insn, at recog.c:2671
Date: Tue, 14 Dec 2021 02:07:48 +0000	[thread overview]
Message-ID: <bug-103676-4-zKDxvKUjpv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103676-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #16 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Here is the most reduced testcase, I could make it:
typedef unsigned long long uint64_t;
struct timer {
 int active;
 uint64_t expire;
 void *arg;
};
int irq_disable();
void irq_restore(int);
static inline uint64_t h(const  uint64_t *p64)
{
 uint64_t tmp;
 asm(
  "ldrd %Q[r], %R[r], %[p]\n"
  : [r]"=lh"(tmp)
  : [p]"m"(*p64)
  : "memory"
 );
 return tmp;
}
uint64_t monotonic;
void timer_callout(timer *tmr, uint64_t nsec, void *arg)
{
 const int s = irq_disable();
 if (tmr->active)
   tmr->arg = arg;
 tmr->expire = h(&monotonic) + 100000 + (nsec == 1 ? 0 : nsec);
 irq_restore(s);
}

  parent reply	other threads:[~2021-12-14  2:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-12 22:32 [Bug target/103676] New: " patrick.oppenlander at gmail dot com
2021-12-12 23:31 ` [Bug target/103676] " pinskia at gcc dot gnu.org
2021-12-12 23:32 ` pinskia at gcc dot gnu.org
2021-12-12 23:54 ` patrick.oppenlander at gmail dot com
2021-12-12 23:58 ` patrick.oppenlander at gmail dot com
2021-12-13 22:56 ` patrick.oppenlander at gmail dot com
2021-12-13 23:06 ` pinskia at gcc dot gnu.org
2021-12-13 23:13 ` pinskia at gcc dot gnu.org
2021-12-14  0:48 ` patrick.oppenlander at gmail dot com
2021-12-14  0:48 ` patrick.oppenlander at gmail dot com
2021-12-14  0:51 ` pinskia at gcc dot gnu.org
2021-12-14  0:52 ` pinskia at gcc dot gnu.org
2021-12-14  1:16 ` patrick.oppenlander at gmail dot com
2021-12-14  1:17 ` patrick.oppenlander at gmail dot com
2021-12-14  1:48 ` pinskia at gcc dot gnu.org
2021-12-14  1:50 ` [Bug target/103676] [10/11/12 Regression] " pinskia at gcc dot gnu.org
2021-12-14  2:07 ` pinskia at gcc dot gnu.org [this message]
2021-12-14  2:11 ` pinskia at gcc dot gnu.org
2021-12-14  2:15 ` pinskia at gcc dot gnu.org
2021-12-29 17:02 ` jakub at gcc dot gnu.org
2021-12-29 17:06 ` jakub at gcc dot gnu.org
2022-01-17 12:46 ` rguenth at gcc dot gnu.org
2022-01-17 16:43 ` vmakarov at gcc dot gnu.org
2022-01-17 17:00 ` jakub at gcc dot gnu.org
2022-01-18 13:38 ` vmakarov at gcc dot gnu.org
2022-01-21 18:37 ` cvs-commit at gcc dot gnu.org
2022-01-28 16:38 ` [Bug target/103676] [10/11 " jakub at gcc dot gnu.org
2022-06-28 10:47 ` jakub at gcc dot gnu.org
2023-07-07 10:41 ` [Bug target/103676] [11 " rguenth 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-103676-4-zKDxvKUjpv@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).