From: David Edelsohn <dje.gcc@gmail.com>
To: Diego Novillo <dnovillo@google.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: VEC re-write [patch 01/25]
Date: Mon, 19 Nov 2012 01:14:00 -0000 [thread overview]
Message-ID: <CAGWvnynkSgGru8jmeUfQqAht32JLusbap5R4rNAhhWSj1AYwhw@mail.gmail.com> (raw)
In-Reply-To: <CAD_=9DQVqL-dKGdZoL=mm6Z_6OMKXG4J+TdDHU9xFJx01eiCJQ@mail.gmail.com>
On Sun, Nov 18, 2012 at 8:03 PM, Diego Novillo <dnovillo@google.com> wrote:
>> And now bootstrap fails on AIX using GCC 4.6.3 with the error:
>>
>> /nasfarm/dje/src/src/gcc/c-family/c-lex.c: In function 'c_fileinfo*
>> get_fileinfo(const char*)':
>> /nasfarm/dje/src/src/gcc/c-family/c-lex.c:107:39: error: overloaded
>> function with no contextual type information
>>
>> which is
>>
>> file_info_tree = splay_tree_new ((splay_tree_compare_fn) strcmp,
>> 0,
>> (splay_tree_delete_value_fn) free);
>>
>
> Odd. The patch did not touch c-lex.c.
I opened PR 55384 to track this
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55384
The problem is AIX stdlib.h defines
#define vec_free free
and vec.h
defines two functions named vec_free()
With the VEC changes, these now are renamed "free" and lead to
ambiguous name resolution.
I am not sure where
#undef vec_free
should be placed. In vec.h or system.h?
Thanks, David
next prev parent reply other threads:[~2012-11-19 1:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 21:28 David Edelsohn
2012-11-19 1:04 ` Diego Novillo
2012-11-19 1:14 ` David Edelsohn [this message]
2012-11-19 3:18 ` Ian Lance Taylor
2012-11-19 14:46 ` David Edelsohn
-- strict thread matches above, loose matches on Subject: below --
2012-11-15 21:53 Diego Novillo
[not found] ` <50A61414.8070908@redhat.com>
2012-11-16 12:13 ` Diego Novillo
2012-11-16 12:22 ` Pedro Alves
2012-11-16 23:16 ` Ian Lance Taylor
2012-11-18 2:57 ` Diego Novillo
2012-11-18 17:05 ` Hans-Peter Nilsson
2012-11-18 17:12 ` Diego Novillo
2012-11-18 17:43 ` Hans-Peter Nilsson
2012-11-18 17:48 ` Diego Novillo
2012-11-18 19:15 ` Andrew Pinski
2012-11-19 19:57 ` Jack Howarth
2012-11-19 20:16 ` Jack Howarth
2012-11-25 13:11 ` Richard Biener
2012-11-25 15:25 ` Diego Novillo
2012-11-18 18:25 ` Andreas Tobler
2012-11-18 19:12 ` Hans-Peter Nilsson
2012-11-18 19:32 ` Andreas Tobler
2012-11-18 19:50 ` Hans-Peter Nilsson
2012-11-20 13:57 ` Ulrich Weigand
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=CAGWvnynkSgGru8jmeUfQqAht32JLusbap5R4rNAhhWSj1AYwhw@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@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).