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 c/21438] Warning about division by zero depends on lexical form
Date: Tue, 28 Sep 2021 08:25:09 +0000	[thread overview]
Message-ID: <bug-21438-4-hlG7ykB8km@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-21438-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |pinskia at gcc dot gnu.org
   Last reconfirmed|2005-12-18 01:45:12         |2021-9-28
      Known to fail|                            |

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Manuel López-Ibáñez from comment #5)
> Subject: Bug 21438

The only thing this patch did was uniformed the code between the front-ends.

I am going to look into fix this once and for all.
GCC is the only compiler which warns for this case even.

       reply	other threads:[~2021-09-28  8:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-21438-4@http.gcc.gnu.org/bugzilla/>
2021-09-28  8:25 ` pinskia at gcc dot gnu.org [this message]
     [not found] <bug-21438-6@http.gcc.gnu.org/bugzilla/>
2007-01-16  0:57 ` patchapp at dberlin dot org
2007-03-12  1:32 ` patchapp at dberlin dot org
2007-03-14 18:38 ` manu at gcc dot gnu dot org
2007-03-14 18:39 ` manu at gcc dot gnu dot org
2005-05-07  8:09 [Bug c/21438] New: " neil at gcc dot gnu dot org
2005-05-07 18:18 ` [Bug c/21438] " pinskia at gcc dot gnu dot org
2005-05-07 18:20 ` pinskia at gcc dot gnu dot 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-21438-4-hlG7ykB8km@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).