From: Tristan Gingold <gingold@adacore.com>
To: binutils Development <binutils@sourceware.org>
Subject: [Patch/committed]: Explain PEF and XSYM files
Date: Thu, 19 Jan 2012 11:45:00 -0000 [thread overview]
Message-ID: <8DEEE13C-EBD1-419B-9059-6C913087905C@adacore.com> (raw)
Hi,
I am committing this patch that explains (in a few words) what are the PEF and XSYM files.
Just in case (like me) you were/are wondering.
I haven't found any pointers to the now mysterious per xlib format.
Tristan.
bfd/
2012-01-19 Tristan Gingold <gingold@adacore.com>
* pef.c: Add a comment.
* xsym.c: Likewise.
Index: pef.c
===================================================================
RCS file: /cvs/src/src/bfd/pef.c,v
retrieving revision 1.33
diff -c -r1.33 pef.c
*** pef.c 11 Jul 2011 15:03:07 -0000 1.33
--- pef.c 19 Jan 2012 11:41:44 -0000
***************
*** 19,24 ****
--- 19,28 ----
Foundation, Inc., 51 Franklin Street - Fifth Floor, Boston,
MA 02110-1301, USA. */
+ /* PEF (Preferred Executable Format) is the binary file format for late
+ classic Mac OS versions (before Darwin). It is supported by both m68k
+ and PowerPc. It is also called CFM (Code Fragment Manager). */
+
#include "sysdep.h"
#include "safe-ctype.h"
#include "pef.h"
Index: xsym.c
===================================================================
RCS file: /cvs/src/src/bfd/xsym.c,v
retrieving revision 1.30
diff -c -r1.30 xsym.c
*** xsym.c 11 Jul 2011 15:03:07 -0000 1.30
--- xsym.c 19 Jan 2012 11:41:45 -0000
***************
*** 19,24 ****
--- 19,26 ----
Foundation, Inc., 51 Franklin Street - Fifth Floor, Boston,
MA 02110-1301, USA. */
+ /* xSYM is the debugging format used by CodeWarrior on Mac OS classic. */
+
#include "alloca-conf.h"
#include "sysdep.h"
#include "xsym.h"
reply other threads:[~2012-01-19 11:45 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=8DEEE13C-EBD1-419B-9059-6C913087905C@adacore.com \
--to=gingold@adacore.com \
--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).