public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: "Mark E." <snowball3@usa.net>
To: gas2@cygnus.com
Subject: A little more on the 2.10 COFF problem
Date: Fri, 09 Oct 1998 09:49:00 -0000	[thread overview]
Message-ID: <199810091648.QAA53554@out5.ibm.net> (raw)

Setup: DJGPP (COFF) and with binutils sources 2.9.1 & Oct 8 2.10 
snapshot.

The problem is that while the 2.10 snapshot generates object files of 
the exact same length as 2.9, the 2.10 object file is different despite 
using the same input file. I don't think there's supposed to a difference 
in object files produces by such a simple program:

#include <stdio.h>

int main()
{
  printf("Hello World!\n");
  return 0;
}

And the program generated by the 2.10's as.exe and ld.exe doesn't run 
either. When compiling 2.10 with 2.10 exe's, object file warnings 
appear that didn't when 2.10 is compiled with 2.9.

If someone could confirm what I'm pointing out, I'd much appreciate it, 
thanks.

Mark

-- 
Mark E. snowball3@usa.net
http://members.xoom.com/snowball3/

                 reply	other threads:[~1998-10-09  9:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=199810091648.QAA53554@out5.ibm.net \
    --to=snowball3@usa.net \
    --cc=gas2@cygnus.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).