public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: joel@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org
Cc: pirovano.thysys@tiscalinet.it, ccj@acm.org
Subject: other/8314: m68k-elf/rtems should multilib crt[begin|end].o
Date: Tue, 22 Oct 2002 15:46:00 -0000 [thread overview]
Message-ID: <20021022223628.19734.qmail@sources.redhat.com> (raw)
>Number: 8314
>Category: other
>Synopsis: m68k-elf/rtems should multilib crt[begin|end].o
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: wrong-code
>Submitter-Id: net
>Arrival-Date: Tue Oct 22 15:46:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: joel@gcc.gnu.org
>Release: gcc 3.2
>Organization:
>Environment:
Target m68k-elf and m68k-rtems
>Description:
crtbegin.o and crtend.o are compiled from C and
when must be compiled with appropriate CPU options
to generate correct code on coldfire models.
>How-To-Repeat:
>Fix:
2002-10-22 Joel Sherrill <joel@OARcorp.com>
* config/m68k/t-crtstuff: Include crti.o, crtn.o, crtbegin.o
and crtend.o as multilib items.
diff -uNr /usr1/rtems/work-tools/original/gcc-3.2/gcc/config/m68k/t-crtstuff gcc-3.2/gcc/config/m68k/t-crtstuff
--- /usr1/rtems/work-tools/original/gcc-3.2/gcc/config/m68k/t-crtstuff Tue Sep 14 04:52:09 1999
+++ gcc-3.2/gcc/config/m68k/t-crtstuff Tue Oct 22 17:24:52 2002
@@ -1,5 +1,4 @@
-# from ../t-svr4
-EXTRA_PARTS=crtbegin.o crtend.o crti.o crtn.o
+EXTRA_MULTILIB_PARTS=crtbegin.o crtend.o crti.o crtn.o
# Add flags here as required.
CRTSTUFF_T_CFLAGS =
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-10-22 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 15:46 joel [this message]
2002-10-22 15:50 joel
2002-10-23 10:15 joel
2002-11-10 22:03 mmitchel
2002-11-19 15:10 Joel Sherrill
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=20021022223628.19734.qmail@sources.redhat.com \
--to=joel@gcc.gnu.org \
--cc=ccj@acm.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=pirovano.thysys@tiscalinet.it \
/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).