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 tree-optimization/101466] Optimizers should fold bounds checking for -D_GLIBCXX_ASSERTIONS=1
Date: Thu, 15 Jul 2021 19:39:09 +0000	[thread overview]
Message-ID: <bug-101466-4-vOqrpmLnm1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101466-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to cqwrteur from comment #2)
> The --enable-libstdcxx-verbose has side effects, not optimizing to
> vectorization code is correct, although

Those can be merged still since the arguments to __replacement_assert are all
the same, you can change my reduced testcase to do something similar as
__replacement_assert really.  The problem is the merging of the if don't happen
if there is an statement inbetween.

  parent reply	other threads:[~2021-07-15 19:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-15 19:18 [Bug tree-optimization/101466] New: " unlvsur at live dot com
2021-07-15 19:22 ` [Bug tree-optimization/101466] " unlvsur at live dot com
2021-07-15 19:27 ` [Bug tree-optimization/101466] Optimizers should fold bounds checking for -D_GLIBCXX_ASSERTIONS=1 + --disable-libstdcxx-verbose unlvsur at live dot com
2021-07-15 19:28 ` unlvsur at live dot com
2021-07-15 19:32 ` [Bug tree-optimization/101466] Optimizers should fold bounds checking for -D_GLIBCXX_ASSERTIONS=1 pinskia at gcc dot gnu.org
2021-07-15 19:39 ` pinskia at gcc dot gnu.org [this message]
2021-07-15 19:40 ` unlvsur at live dot com
2021-07-15 19:53 ` pinskia at gcc dot gnu.org
2021-07-16  6:29 ` rguenth at gcc dot gnu.org
2021-07-16  6:50 ` unlvsur at live dot com
2021-07-16  6:54 ` rguenth at gcc dot gnu.org
2021-07-16  6:57 ` rguenth at gcc dot gnu.org
2021-07-16  7:03 ` rguenth at gcc dot gnu.org
2021-07-19 14:15 ` unlvsur at live dot com
2021-07-20  7:07 ` rguenther at suse dot de
2021-08-02 18:05 ` unlvsur at live dot com

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-101466-4-vOqrpmLnm1@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).