public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/16030] [3.4/3.5 Regression] [cygwin/mingw]: stdcall function decoration vs LTHUNK alias in multiple inheritanc
Date: Thu, 12 Aug 2004 14:35:00 -0000	[thread overview]
Message-ID: <20040812143530.28546.qmail@sourceware.org> (raw)
In-Reply-To: <20040617025326.16030.dannysmith@users.sourceforge.net>


------- Additional Comments From mark at codesourcery dot com  2004-08-12 14:35 -------
Subject: Re:  [3.4/3.5 Regression] [cygwin/mingw]: stdcall
 function decoration vs LTHUNK alias in multiple inheritanc

steven at gcc dot gnu dot org wrote:

>------- Additional Comments From steven at gcc dot gnu dot org  2004-08-12 08:15 -------
>Mark, can you review the patch at 
>http://gcc.gnu.org/ml/gcc-patches/2004-07/msg00534.html? 
>  
>
As a minor point, the get_identifier bit of that patch is very 
inefficient.  Instead, assemble_alias should be modified to take a "char 
*" argument, or a new function should be created that both 
assemble_alias and make_alias_fr_thunk can use.

But, a more major point is that I'm not at all confident that it's 
correct to use the encoded name on all targets.  Maybe 
ASM_OUTPUT_DEF_FROM_DECLS should be defined for these targets instead?



-- 


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


  parent reply	other threads:[~2004-08-12 14:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17  2:53 [Bug c++/16030] New: " dannysmith at users dot sourceforge dot net
2004-07-07  1:04 ` [Bug c++/16030] " dannysmith at users dot sourceforge dot net
2004-07-07  1:07 ` [Bug c++/16030] [3.4/3.5 Regression] " pinskia at gcc dot gnu dot org
2004-08-12  8:15 ` steven at gcc dot gnu dot org
2004-08-12 14:35 ` mark at codesourcery dot com [this message]
2004-08-18 10:07 ` dannysmith at users dot sourceforge dot net
2004-08-19 21:21 ` mmitchel at gcc dot gnu dot org
2004-08-21  8:02 ` cvs-commit at gcc dot gnu dot org
2004-08-21  8:05 ` [Bug c++/16030] [3.4 " dannysmith at users dot sourceforge dot net
2004-08-23  6:54 ` mark at codesourcery dot com
2004-08-29 18:53 ` mmitchel at gcc dot gnu dot org
2004-10-31  2:01 ` mmitchel at gcc dot gnu dot org
2004-10-31  2:05 ` giovannibajo at libero dot it
2004-10-31  2:37 ` dannysmith at users dot sourceforge dot net
2005-05-19 17:27 ` mmitchel at gcc dot gnu dot 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=20040812143530.28546.qmail@sourceware.org \
    --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).