Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@cygnus.com>
To: David Edelsohn <dje@watson.ibm.com>
Cc: Elena Zannoni <ezannoni@cygnus.com>,
	Kevin Buettner <kevinb@cygnus.com>,
	"Zack Weinberg" <zackw@Stanford.EDU>,
	Matthew Conway <matt_conway@i2.com>,
	Mark Mitchell <mark@codesourcery.com>,
	gcc-patches@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: Limited success with 3.0 branch on AIX
Date: Wed, 16 May 2001 12:24:00 -0000	[thread overview]
Message-ID: <15106.54247.107624.415502@kwikemart.cygnus.com> (raw)
In-Reply-To: <200105161814.OAA25626@makai.watson.ibm.com>

David Edelsohn writes:
 > 	As a follow up, compiling file bss.c with IBM's XLC compiler
 > produces bss.o containing:
 > 
 > [0]     m   0x00000000        -2     3    0x67         0x0003     .file
 > [1]     a0                                                        bss.c
 > [2]     a0                                                        Wed May 16 14:08:13 2001 
 > [3]     a0                                                        IBM C and C++ Compilers Version 3.6.6.0 --- 
 > 
 > Disassembling bss.o produces an assembly file containing the directive
 > 
 > 	.file   "bss.c"
 > 
 > Assembling the disassembled file produces a new object file containing:
 > 
 > [0]     m   0x00000000        -2     1    0x67         0x0003     .file
 > [1]     a0                                                        bss.c
 > 
 > 
 > 	IBM's AIX assembler (and the GNU assembler) do not allow access to
 > all of the user-settable internal structure of XCOFF files.  This is a
 > known limitation.  There is no way to insert the information into the most
 > appropriate XCOFF location for compiler version or compiler-defined
 > information. 

Obviously this prompts the question: can the limitation be eliminated, i.e.
can the correct functionality be provided? 

If not, we'll have to use a different approach. And looks like using C_GSYM
could be the one.


Elena


 > 
 > David
 > 


  reply	other threads:[~2001-05-16 12:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200104302116.RAA23290@makai.watson.ibm.com>
2001-05-02 23:25 ` Zack Weinberg
2001-05-03  1:42   ` Kevin Buettner
2001-05-15 15:27     ` Elena Zannoni
2001-05-15 15:31       ` David Edelsohn
2001-05-15 16:19         ` Elena Zannoni
2001-05-16 10:46           ` David Edelsohn
2001-05-16 11:15           ` David Edelsohn
2001-05-16 12:24             ` Elena Zannoni [this message]
     [not found] <15106.54023.177141.275660@kwikemart.cygnus.com>
2001-05-16 12:37 ` David Edelsohn
2001-05-16 13:07 ` David Edelsohn
2001-05-16 13:51   ` Kevin Buettner
2001-05-16 14:06     ` Stan Shebs
2001-05-16 14:10       ` David Edelsohn
2001-05-16 14:32     ` Elena Zannoni
2001-05-16 21:29   ` Elena Zannoni
2001-05-17 15:27     ` David Edelsohn
     [not found] <OF70310855.A41D4A39-ON86256A39.00616113@i2.com>
2001-05-01 10:13 ` David Edelsohn
2001-05-01 13:02   ` Daniel Berlin
2001-05-01 13:22     ` David Edelsohn
2001-05-01 15:40       ` Kevin Buettner
2001-05-01 15:44         ` David Edelsohn
2001-05-01 16:21   ` Kevin Buettner
2001-05-01 19:15     ` David Edelsohn

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=15106.54247.107624.415502@kwikemart.cygnus.com \
    --to=ezannoni@cygnus.com \
    --cc=dje@watson.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=kevinb@cygnus.com \
    --cc=mark@codesourcery.com \
    --cc=matt_conway@i2.com \
    --cc=zackw@Stanford.EDU \
    /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