public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Mauricio Alvarez <alvarez@ac.upc.edu>
To: binutils@sourceware.org
Subject: Re: problems with gas in AIX 5.2
Date: Mon, 15 May 2006 22:39:00 -0000	[thread overview]
Message-ID: <4468622C.8050307@ac.upc.edu> (raw)
In-Reply-To: <44685480.6060505@redhat.com>

Nick Clifton wrote:
> Hi Mauricio,

Hi Nick and others

thanks for your reply

> 
> Why not use gcc-4.0.2 to assemble the file as well ?  ie why use a
> different assembler from the one that forms part of the gcc-4.0.2
> toolchain ?

I have built gcc-4.0.2 with the native (IBM) assembler and linker, with
 these toolchain "my" application compiles and assembles correctly. I
can not build gcc with binutils because there is some documented
problems of building gcc with binutils on AIX 5.2.

But, I want to use binutils because I want to do some modifications in
the assembler. So, I have to build gcc with the native assembler and to
assemble my applications with the GNU assembler using the mentioned scheme:

powerpc-ibm-aix5.2.0.0-gcc-4.0.2 [...] -S -o file.s file.c
binutils-2.16.1/as -mppc -o file.o file.s

But, using this approach the application (FFMPEG) breaks with a
segmentation fault.

By looking at the generated binaries I think that the problem is in the
GNU assembler.

Then, my original question is: is this a known problem of binutils in
AIX-5.X, and if there is a patch or some compile/assembly options that
can overcome or avoid this problem.

Thanks for your comments.

Mauricio Alvarez

  reply	other threads:[~2006-05-15 11:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-12 22:16 Mauricio Alvarez
2006-05-15 22:38 ` Nick Clifton
2006-05-15 22:39   ` Mauricio Alvarez [this message]
2006-05-19 12:35     ` Nick Clifton

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=4468622C.8050307@ac.upc.edu \
    --to=alvarez@ac.upc.edu \
    --cc=binutils@sourceware.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).