public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "364961 at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105393] A simple for loop becomes an infinite when -O1/2/3 used
Date: Wed, 27 Apr 2022 07:08:52 +0000	[thread overview]
Message-ID: <bug-105393-4-GUfmHzYJEW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105393-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Laryushin Aleksandr <364961 at mail dot ru> ---
Sorry, this is my first bug report.

>Среда, 27 апреля 2022, 9:54 +03:00 от jakub at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org>:
> 
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105393
>
>Jakub Jelinek <jakub at gcc dot gnu.org> changed:
>
>           What |Removed |Added
>----------------------------------------------------------------------------
>         Resolution|FIXED |INVALID
>
>--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
>Please don't change the RESOLVED INVALID status, that is the right thing, there
>was nothing fixed on the GCC side because the testcase was invalid.
>
>--
>You are receiving this mail because:
>You reported the bug. 


Best regards, Laryushin Aleksandr

      parent reply	other threads:[~2022-04-27  7:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26 12:08 [Bug c++/105393] New: " 364961 at mail dot ru
2022-04-26 12:12 ` [Bug c++/105393] " pinskia at gcc dot gnu.org
2022-04-26 12:17 ` 364961 at mail dot ru
2022-04-26 12:32 ` jakub at gcc dot gnu.org
2022-04-27  6:51 ` 364961 at mail dot ru
2022-04-27  6:54 ` jakub at gcc dot gnu.org
2022-04-27  7:08 ` 364961 at mail dot ru [this message]

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-105393-4-GUfmHzYJEW@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).