public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104243] Optimization requires __sync_synchronize
Date: Thu, 27 Jan 2022 08:38:13 +0000 [thread overview]
Message-ID: <bug-104243-4-gFvnOxZmib@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104243-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104243
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to A. Klitzing from comment #5)
> Created attachment 52294 [details]
> assembler output
>
> By the way... If idx is not initialized it will work, too.
>
> @@ -4,7 +4,7 @@
> int main(int argc, char** argv)
> {
> const QString pVersion = QStringLiteral("1.12.2");
> - int idx = 0;
> + int idx;
> const auto& version = QVersionNumber::fromString(pVersion, &idx);
>
> // #ifdef Q_CC_GNU
You were lucky in this case ;)
Anyway, upstream removed the pure attribute as we suggested:
https://codereview.qt-project.org/c/qt/qtbase/+/392357
next prev parent reply other threads:[~2022-01-27 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 14:37 [Bug c++/104243] New: " aklitzing at gmail dot com
2022-01-26 15:07 ` [Bug c++/104243] " rguenth at gcc dot gnu.org
2022-01-26 15:10 ` marxin at gcc dot gnu.org
2022-01-26 15:10 ` marxin at gcc dot gnu.org
2022-01-26 15:14 ` marxin at gcc dot gnu.org
2022-01-26 15:19 ` aklitzing at gmail dot com
2022-01-27 8:38 ` marxin at gcc dot gnu.org [this message]
2022-01-27 17:02 ` thiago at kde dot org
2022-01-27 17:33 ` marxin at gcc dot gnu.org
2022-01-28 7:39 ` 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-104243-4-gFvnOxZmib@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).