From: MFLD <mfld.fr@gmail.com>
To: ELKS <Linux-8086@Vger.Kernel.Org>
Subject: [PATCH PROPOSAL] Bcc: Force initial .text directive
Date: Sat, 11 Apr 2015 18:02:28 +0200 [thread overview]
Message-ID: <55294594.7030903@gmail.com> (raw)
Hello,
Here is a patch proposal to force the insertion of a .text directive at
the beginning of the bcc-cc1 output file.
This is because Bcc makes the assumption that the as86 assembler starts
with the code segment.
This patch prevents the compilation to fail if migrating to another
assembler with a different assumption.
MFLD
diff --git a/bcc/codefrag.c b/bcc/codefrag.c
index d796810..80bab18 100644
--- a/bcc/codefrag.c
+++ b/bcc/codefrag.c
@@ -592,7 +592,8 @@
typedef fastin_t seg_t; /* range 0..3 */
-PRIVATE seg_t segment; /* current seg, depends on init to CSEG =
0 */
+/* Initialize to -1 to force initial segment directive */
+PRIVATE seg_t segment = -1; /* current segment */
/* add carry resulting from char addition */
reply other threads:[~2015-04-11 16:02 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=55294594.7030903@gmail.com \
--to=mfld.fr@gmail.com \
--cc=Linux-8086@Vger.Kernel.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).