From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Graziano Servizi <Graziano.Servizi@bo.infn.it>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: question
Date: Mon, 21 Jul 2014 09:10:00 -0000 [thread overview]
Message-ID: <CAH6eHdTX+iHeANOOmruUQtDkbNWiu=ddoUm8tpmcAjWrkgJQPw@mail.gmail.com> (raw)
In-Reply-To: <53CCD481.60201@bo.infn.it>
On 21 July 2014 09:51, Graziano Servizi wrote:
> Is there an "undefined behaviour" in the following short code?
>
>
> //
> # include <iostream>
> # include <functional>
>
> int main( )
> {
> int c = 90;
> double r = 70;
> auto v = [c] (double c)
> {std::cout << "homonymous dummy argument ... " << c << std::endl;};
> v(r);
> }
>
>
> //
>
> I ask this because the gnu-gcc compiler prints out the value of the
> "captured" int c = 90 variable, while clang prints the value of the double r
> = 70 transmitted argument instead...
It looks like a GCC bug, please report it to Bugzilla.
next prev parent reply other threads:[~2014-07-21 9:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 8:51 question Graziano Servizi
2014-07-21 9:10 ` Jonathan Wakely [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-29 9:03 Question Mo Alamili
2022-12-02 9:06 ` Question Mo Alamili
[not found] <20200831201750.74266362@arch.localdomain>
[not found] ` <20200903232726.ba28157e5ee86c0dbd76f723@wp.pl>
2020-09-04 22:49 ` Question, using gcc, forum tele
2020-09-04 23:44 ` Question tele
2014-10-07 13:57 Question Graziano Servizi
2014-10-12 12:54 ` Question David Hagood
2014-10-13 9:55 ` Question Jonathan Wakely
2014-02-03 17:37 question Graziano Servizi
2014-02-03 17:53 ` question Ángel González
2014-02-04 8:11 ` question Jonathan Wakely
2005-10-29 21:02 Question Matias Trocki
2005-10-30 5:00 ` Question Ian Lance Taylor
2004-12-02 15:11 Question Roberto Ausas
2004-12-02 15:25 ` Question Leopold Palomo-Avellaneda
2004-12-02 15:36 ` Question Eljay Love-Jensen
2004-08-19 16:21 question balan
2004-08-19 16:27 ` question Eljay Love-Jensen
2002-06-13 16:17 question Brett Hunt
2002-06-13 10:54 question Antonio Fontinha
1999-12-15 11:06 question petar
1999-12-31 22:24 ` question petar
1999-10-18 10:03 Question Rui Pedro Fernandes
1999-10-31 13:57 ` Question Rui Pedro Fernandes
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='CAH6eHdTX+iHeANOOmruUQtDkbNWiu=ddoUm8tpmcAjWrkgJQPw@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=Graziano.Servizi@bo.infn.it \
--cc=gcc-help@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).