public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "admin@tho-otto.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/115010] m68k: invalid subl instruction generated
Date: Mon, 13 May 2024 03:20:54 +0000	[thread overview]
Message-ID: <bug-115010-4-Dpdn4rX3Hn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115010-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Thorsten Otto <admin@tho-otto.de> ---
Confirmed, reverting that commit will prevent the error. Now the question is
how to find the real cause of the problem, since reverting that commit is most
likely not the solution. OTOH, it would be nice to know why the call to
emit_clobber() originally was done.

  parent reply	other threads:[~2024-05-13  3:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09 12:21 [Bug target/115010] New: " admin@tho-otto.de
2024-05-09 14:50 ` [Bug target/115010] " schwab@linux-m68k.org
2024-05-09 15:13 ` admin@tho-otto.de
2024-05-09 16:11 ` pinskia at gcc dot gnu.org
2024-05-09 16:32 ` admin@tho-otto.de
2024-05-09 16:33 ` pinskia at gcc dot gnu.org
2024-05-09 16:34 ` sjames at gcc dot gnu.org
2024-05-09 16:46 ` admin@tho-otto.de
2024-05-09 17:15 ` admin@tho-otto.de
2024-05-09 17:17 ` admin@tho-otto.de
2024-05-09 18:51 ` admin@tho-otto.de
2024-05-12 15:24 ` mikpelinux at gmail dot com
2024-05-13  3:20 ` admin@tho-otto.de [this message]
2024-05-13  9:52 ` admin@tho-otto.de
2024-05-13 10:01 ` admin@tho-otto.de
2024-05-13 11:35 ` admin@tho-otto.de
2024-05-23  5:03 ` pinskia at gcc dot gnu.org
2024-05-23  5:17 ` admin@tho-otto.de

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-115010-4-Dpdn4rX3Hn@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).