public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daniel.f.starke at freenet dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100461] [11/12 Regression] mingw build broken due to change of rdtsc implementation
Date: Fri, 07 May 2021 17:13:48 +0000	[thread overview]
Message-ID: <bug-100461-4-pUoPbbf9rK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100461-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Daniel Starke <daniel.f.starke at freenet dot de> ---
Thank you for the suggestion, however, I am not involved in the mingw-w64
project. Furthermore, the fact that this regression remains against all
versions of mingw-w64 known to date does not change.
It is also unclear to me why only these two intrinsics are handled differently
now. What was the purpose of this change? Do we break existing code if the
change is reverted?

  parent reply	other threads:[~2021-05-07 17:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 20:14 [Bug target/100461] New: " daniel.f.starke at freenet dot de
2021-05-06 20:54 ` [Bug target/100461] " ubizjak at gmail dot com
2021-05-06 22:29 ` pinskia at gcc dot gnu.org
2021-05-06 22:54 ` hjl.tools at gmail dot com
2021-05-07  4:25 ` daniel.f.starke at freenet dot de
2021-05-07  7:15 ` rguenth at gcc dot gnu.org
2021-05-07 12:11 ` hjl.tools at gmail dot com
2021-05-07 17:13 ` daniel.f.starke at freenet dot de [this message]
2021-05-07 19:49 ` hjl.tools at gmail dot com
2022-05-14  6:22 ` daniel.f.starke at freenet dot de
2022-05-14  7:07 ` redi 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-100461-4-pUoPbbf9rK@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).