From: Harshad R Joglekar <harshad.joglekar@wipro.com>
To: binutils@sources.redhat.com
Subject: [asm] Difference of symbols in another section
Date: Sat, 08 Sep 2001 03:49:00 -0000 [thread overview]
Message-ID: <3B99F88A.BCF5D689@wipro.com> (raw)
Hi Alan,
You had submitted the below patch for assembler (expr.c),
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/gas/expr.c.diff?r1=1.33&r2=1.34&cvsroot=src&f=h
and then you reverted it in the next revision !! I couldn't find any
message descrbing either of the changes.
The patch was useful in the following case:
-----------------------------------------------
.data
foo:
.word 0x00
bar:
.text
start:
jmp start + (bar - foo)
---------------------------------------------
The i386 and ARM assemblers parse this with default options,
but complain when listings are enabled.
The patch you had submitted corrected the problem, and I did not find
any side-effects, although I have not tested it thoroughly.
If there are no issues, can you reapply that patch?
regards,
Harshad
next reply other threads:[~2001-09-08 3:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-08 3:49 Harshad R Joglekar [this message]
2001-09-08 6:30 ` Alan Modra
[not found] <200109081344.f88Diif16713@harshad.wipro.com>
2001-09-08 8:02 ` Harshad R Joglekar
2001-09-09 6:56 ` Alan Modra
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=3B99F88A.BCF5D689@wipro.com \
--to=harshad.joglekar@wipro.com \
--cc=binutils@sources.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).