public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bekenn at yopmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/54170] Call to lambda elided
Date: Mon, 06 Aug 2012 08:11:00 -0000	[thread overview]
Message-ID: <bug-54170-4-SnBzPcEgS2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54170-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54170

--- Comment #8 from bekenn at yopmail dot com 2012-08-06 08:11:38 UTC ---
(In reply to comment #4)
> If submitter can try current 4_7-branch or mainline, it would be easy for him
> to double check.

I installed mint in a virtual machine to test those, but I couldn't get either
trunk or gcc-4_7 to build; I got these errors, which I haven't bothered to
investigate:

build/gengtype.o: In function `create_optional_field_':
/home/bekenn/Projects/gcc-build/gcc/../../gcc-4_7/gcc/gengtype.c:853: undefined
reference to `lexer_line'
build/gengtype.o: In function `adjust_field_rtx_def':
/home/bekenn/Projects/gcc-build/gcc/../../gcc-4_7/gcc/gengtype.c:989: undefined
reference to `lexer_line'
/home/bekenn/Projects/gcc-build/gcc/../../gcc-4_7/gcc/gengtype.c:1045:
undefined reference to `lexer_line'
/home/bekenn/Projects/gcc-build/gcc/../../gcc-4_7/gcc/gengtype.c:1055:
undefined reference to `lexer_line'
/home/bekenn/Projects/gcc-build/gcc/../../gcc-4_7/gcc/gengtype.c:1121:
undefined reference to `lexer_line'
build/gengtype.o:/home/bekenn/Projects/gcc-build/gcc/../../gcc-4_7/gcc/gengtype.c:1160:
more undefined references to `lexer_line' follow
build/gengtype-parse.o: In function `token':
/home/bekenn/Projects/gcc-build/gcc/../../gcc-4_7/gcc/gengtype-parse.c:53:
undefined reference to `yylex'
build/gengtype-parse.o: In function `parse_error':
/home/bekenn/Projects/gcc-build/gcc/../../gcc-4_7/gcc/gengtype-parse.c:142:
undefined reference to `lexer_line'
/home/bekenn/Projects/gcc-build/gcc/../../gcc-4_7/gcc/gengtype-parse.c:142:
undefined reference to `lexer_line'
build/gengtype-parse.o: In function `struct_field_seq':
/home/bekenn/Projects/gcc-build/gcc/../../gcc-4_7/gcc/gengtype-parse.c:692:
undefined reference to `lexer_line'
build/gengtype-parse.o: In function `type':
/home/bekenn/Projects/gcc-build/gcc/../../gcc-4_7/gcc/gengtype-parse.c:726:
undefined reference to `lexer_line'
/home/bekenn/Projects/gcc-build/gcc/../../gcc-4_7/gcc/gengtype-parse.c:758:
undefined reference to `lexer_line'
build/gengtype-parse.o:/home/bekenn/Projects/gcc-build/gcc/../../gcc-4_7/gcc/gengtype-parse.c:758:
more undefined references to `lexer_line' follow
build/gengtype-parse.o: In function `parse_file':
/home/bekenn/Projects/gcc-build/gcc/../../gcc-4_7/gcc/gengtype-parse.c:951:
undefined reference to `yybegin'
/home/bekenn/Projects/gcc-build/gcc/../../gcc-4_7/gcc/gengtype-parse.c:986:
undefined reference to `lexer_toplevel_done'
/home/bekenn/Projects/gcc-build/gcc/../../gcc-4_7/gcc/gengtype-parse.c:991:
undefined reference to `yyend'
collect2: ld returned 1 exit status


  parent reply	other threads:[~2012-08-06  8:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-04  0:03 [Bug c++/54170] New: " bekenn at yopmail dot com
2012-08-04  0:07 ` [Bug c++/54170] " paolo.carlini at oracle dot com
2012-08-04 10:48 ` redi at gcc dot gnu.org
2012-08-04 11:35 ` paolo.carlini at oracle dot com
2012-08-04 11:37 ` paolo.carlini at oracle dot com
2012-08-06  4:44 ` bekenn at yopmail dot com
2012-08-06  4:46 ` bekenn at yopmail dot com
2012-08-06  7:52 ` redi at gcc dot gnu.org
2012-08-06  8:11 ` bekenn at yopmail dot com [this message]
2012-08-06  8:32 ` redi at gcc dot gnu.org
2012-11-30 12:31 ` paolo.carlini at oracle dot com
2012-12-03 16:02 ` paolo at gcc dot gnu.org
2012-12-03 16:10 ` paolo.carlini at oracle dot com
2013-07-10  2:57 ` foom at fuhm dot net
2013-07-10  5:14 ` jason at gcc dot gnu.org
2013-07-10  5:54 ` jason at gcc dot gnu.org
2014-05-24 12:11 ` redi 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=bug-54170-4-SnBzPcEgS2@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).