public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: David Daney <ddaney@avtrex.com>
Cc: binutils@sources.redhat.com
Subject: Re: [Patch] was: MIPS assembler  no longer "combines symbols in different segments"...
Date: Mon, 28 Feb 2005 16:30:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.61L.0502281437290.3578@blysk.ds.pg.gda.pl> (raw)
In-Reply-To: <421FE7A6.7020500@avtrex.com>

On Fri, 25 Feb 2005, David Daney wrote:

> Attached is a patch that fixes this problem.  This one I am much more
> confident of.  It passes make check in libffi for my hacked up back ported to
> gcc-3.4.3 version.  This include the exception test that failed with my last
> patch.
[...]
> 2005-02-35  David Daney  <ddaney@avtrex.com>
> 
> * config/tc-mips.h: #define DIFF_EXPR_OK.
> * config/tc-mips.c (md_apply_fix3): Remove assert (!fixP->fx_pcrel)
> because DIFF_EXPR_OK generates them.
> (tc_gen_reloc) : Handle fixP->fx_pcrel for BFD_RELOC_32 case.

 Have you seen the comment about R_MIPS_PC32 in bfd/elf32-mips.c?  This is 
a GNU extension which we don't want to support for generation of new code.  
It's not even supported by elfn32-mips.c and elf64-mips.c at all, so if 
your GCC uses it for the (n)64 or the n32 ABI, it will not work anyway.

 How about updating GCC so that it does not emit these problematic 
statements?  Either your local copy or the 3.3 branch (if there is 
interest).  Using older binutils is another option.

  Maciej

  parent reply	other threads:[~2005-02-28 14:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-26 19:36 David Daney
2005-02-26 20:19 ` David Daney
2005-02-27  0:09   ` cgd
2005-02-27  1:17   ` David Daney
2005-02-27  2:47 ` [Patch] was: " David Daney
     [not found]   ` <mailpost.1109387217.12843@news-sj1-1>
2005-02-28  9:07     ` cgd
2005-02-28 16:30   ` Maciej W. Rozycki [this message]
2005-02-28 17:15     ` Daniel Jacobowitz
2005-02-28 18:06       ` Dave Korn
2005-02-28 19:00         ` Maciej W. Rozycki
2005-02-28 19:52           ` David Daney
2005-02-28 20:41             ` Maciej W. Rozycki
2005-02-28 20:53               ` David Daney
2005-02-28 22:03                 ` Maciej W. Rozycki
2005-02-28 22:29                   ` David Daney
2005-02-28 23:00                 ` Richard Sandiford
2005-02-28 19:57           ` Dave Korn
2005-02-28 18:36       ` Maciej W. Rozycki

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=Pine.LNX.4.61L.0502281437290.3578@blysk.ds.pg.gda.pl \
    --to=macro@linux-mips.org \
    --cc=binutils@sources.redhat.com \
    --cc=ddaney@avtrex.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).