From: Ian Lance Taylor <ian@zembu.com>
To: scottb@netwinder.org
Cc: binutils@sourceware.cygnus.com
Subject: Re: make check failures...
Date: Mon, 30 Aug 1999 20:15:00 -0000 [thread overview]
Message-ID: <19990830230711.914.qmail@daffy.airs.com> (raw)
In-Reply-To: <37CAC7E5.8440A11F@netwinder.org>
Date: Mon, 30 Aug 1999 14:05:25 -0400
From: scottb <scottb@netwinder.org>
I get the following two failures when running make check on the current
CVS tree on a NetWinder.
Running /home/scottb/cvstree/binutils/gas/testsuite/gas/elf/elf.exp ...
FAIL: elf section0
FAIL: elf section1
I looked into this and found the output different from the .d files it
is compared against. It seems section alignment is to blame. A patch
that fixed it for me is attached.
For an ELF target I would not expect any section alignment of this
sort. The tests pass correctly for me for ELF targets, and indeed
your patch would cause the tests to fail. Your sections appear to be
aligned to 4 byte boundaries. Why is this happening?
Ian
prev parent reply other threads:[~1999-08-30 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-30 11:08 scottb
1999-08-30 20:15 ` Ian Lance Taylor [this message]
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=19990830230711.914.qmail@daffy.airs.com \
--to=ian@zembu.com \
--cc=binutils@sourceware.cygnus.com \
--cc=scottb@netwinder.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).