public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@kam.mff.cuni.cz>
To: ibuclaw at gdcproject dot org <gcc-bugzilla@gcc.gnu.org>
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: [Bug d/103040] [12 Regression] gdc.dg/torture/pr101273.d FAILs
Date: Tue, 2 Nov 2021 21:53:10 +0100	[thread overview]
Message-ID: <20211102205310.GA93151@kam.mff.cuni.cz> (raw)
In-Reply-To: <bug-103040-4-yyDeFokHRC@http.gcc.gnu.org/bugzilla/>

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103040
> 
> --- Comment #15 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
> Got it. The difference between D and C++ is a matter of early inlining.
> 
> The C++ example Jakub posted fails in the same way that D does if you compile
> with: -O1 -fno-inline
Great, I will take a look now (I was travelling that is why i did not
started earlier)

Honza


  reply	other threads:[~2021-11-02 20:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02  9:24 [Bug d/103040] New: " ro at gcc dot gnu.org
2021-11-02  9:24 ` [Bug d/103040] " ro at gcc dot gnu.org
2021-11-02  9:51 ` jakub at gcc dot gnu.org
2021-11-02 10:13 ` jakub at gcc dot gnu.org
2021-11-02 10:29 ` ibuclaw at gdcproject dot org
2021-11-02 10:31 ` jakub at gcc dot gnu.org
2021-11-02 10:44 ` jakub at gcc dot gnu.org
2021-11-02 10:46 ` jakub at gcc dot gnu.org
2021-11-02 11:15 ` ibuclaw at gdcproject dot org
2021-11-02 12:14 ` ibuclaw at gdcproject dot org
2021-11-02 13:41 ` ibuclaw at gdcproject dot org
2021-11-02 14:41 ` ibuclaw at gdcproject dot org
2021-11-02 18:26 ` [Bug d/103040] [12 Regression] " hubicka at gcc dot gnu.org
2021-11-02 19:39 ` jakub at gcc dot gnu.org
2021-11-02 19:57   ` Jan Hubicka
2021-11-02 19:57 ` hubicka at kam dot mff.cuni.cz
2021-11-02 20:28 ` ibuclaw at gdcproject dot org
2021-11-02 20:45 ` ibuclaw at gdcproject dot org
2021-11-02 20:53   ` Jan Hubicka [this message]
2021-11-02 20:53 ` hubicka at kam dot mff.cuni.cz
2021-11-02 21:05 ` hubicka at kam dot mff.cuni.cz
2021-11-03  0:46 ` cvs-commit at gcc dot gnu.org
2021-11-03  8:12 ` marxin at gcc dot gnu.org
2021-11-03 11:36 ` ibuclaw at gdcproject dot org
2021-11-03 11:44 ` marxin 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=20211102205310.GA93151@kam.mff.cuni.cz \
    --to=hubicka@kam.mff.cuni.cz \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-bugzilla@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).