public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Kai Tietz <ktietz70@googlemail.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
		Jason Merrill <jason@redhat.com>,
	Richard Henderson <rth@redhat.com>
Subject: Re: [patch c,c++,i386]:PR/15774 - Conflicting function decls not diagnosed
Date: Wed, 22 Dec 2010 17:38:00 -0000	[thread overview]
Message-ID: <AANLkTikxC7RcHW_vki2agKTKu_NC_wSAwdcsm03Axcyj@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1012221622590.6566@digraph.polyomino.org.uk>

On Wed, Dec 22, 2010 at 10:31 AM, Joseph S. Myers
<joseph@codesourcery.com> wrote:
> On Wed, 22 Dec 2010, Kai Tietz wrote:
>
>> Hi,  this patch fixes the bug described at
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15774 in bugzilla.
>
> Could you please explain more about how and why it fixes the bug?  The bug
> described there is:
>
>    The C++ frontend doesn't always call targetm.compare_type_attributes
>    when comparing function decls in decl.c: decls_match.  As a result
>    conflicting decls are not diagnosed.
>
> But your patch doesn't change the compatibility testing at all; it just
> changes how things are printed.  Is there code somewhere that generates
> strings for type names and compares those strings to determine
> compatibility?

I don't think the patch actually implement compatibility checking.
What it does is to print the conflicting attributes during
diagnostic report.  And that is something that needed to be fixed.
Also, I am skeptical that we should print all attributes.

I think the actual code generation stuff is orthogonal.

-- Gaby

  reply	other threads:[~2010-12-22 16:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22 14:53 Kai Tietz
2010-12-22 14:58 ` Dave Korn
2010-12-22 15:11   ` Kai Tietz
2010-12-22 15:54     ` Gabriel Dos Reis
2010-12-22 16:21       ` Kai Tietz
2010-12-22 16:31         ` Gabriel Dos Reis
2010-12-22 16:38           ` Kai Tietz
2010-12-22 17:21 ` Joseph S. Myers
2010-12-22 17:38   ` Gabriel Dos Reis [this message]
2010-12-22 17:55   ` Kai Tietz
2010-12-22 17:57     ` Joseph S. Myers
2010-12-22 18:03       ` Kai Tietz
2010-12-22 18:10         ` Kai Tietz
2010-12-22 19:13         ` Joseph S. Myers
2010-12-22 18:24   ` Jason Merrill
2010-12-22 19:23     ` Kai Tietz
2010-12-22 19:25       ` Kai Tietz
2010-12-22 20:37         ` Kai Tietz
2010-12-23  8:19       ` Gabriel Dos Reis

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=AANLkTikxC7RcHW_vki2agKTKu_NC_wSAwdcsm03Axcyj@mail.gmail.com \
    --to=gdr@integrable-solutions.net \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=ktietz70@googlemail.com \
    --cc=rth@redhat.com \
    /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).