public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Jessica Han" <jessica@cup.hp.com>
To: "'Richard Henderson'" <rth@redhat.com>
Cc: <gcc@gcc.gnu.org>, <reva@cup.hp.com>
Subject: RE: IA64 ABI Status
Date: Mon, 17 Dec 2001 18:59:00 -0000	[thread overview]
Message-ID: <00fc01c1876f$afadff20$2f65000f@JH761542> (raw)
In-Reply-To: <20011205162610.C8874@redhat.com>


Thank you very much for response. I still have some questions about COMDAT
to bother you:
  Is GCC generating all the information needed for gas to output COMDAT
sections currently? What kind of flags/keywords should the assembler look
for in assembly to identify the information should be put in COMDAT
sections?  I've noticed that GCC generated gnu.linkonce sections, are those
COMDAT sections?  If so, are all COMDAT sections marked by gnu.linkonce? If
not, what's the difference between them?

Thanks.

-----Original Message-----
From: Richard Henderson [mailto:rth@redhat.com]
Sent: Wednesday, December 05, 2001 4:26 PM
To: Jessica Han
Cc: gcc@gcc.gnu.org
Subject: Re: IA64 ABI Status


On Wed, Dec 05, 2001 at 02:36:31PM -0800, Jessica Han wrote:
> Does GCC 3.0.2 on IA64 have COMDAT sections specified by C++ ABI yet?

Sort-of, but not really.  We're still using a gnu binutils feature
that provides similar functionality, but is represented differently
in the ELF object file.  The gnu binutils feature pre-dates the new
ELF spec by at least 4 years.

GCC has little to do with this; it's almost all binutils work.

> If not, is there a plan to implement it and when is it going to be
available?

I don't know of anyone working on it.


r~

  reply	other threads:[~2001-12-18  2:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-05 14:36 Jessica Han
2001-12-05 16:31 ` Richard Henderson
2001-12-17 18:59   ` Jessica Han [this message]
2001-12-17 22:16     ` Richard Henderson

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='00fc01c1876f$afadff20$2f65000f@JH761542' \
    --to=jessica@cup.hp.com \
    --cc=gcc@gcc.gnu.org \
    --cc=reva@cup.hp.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).