public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/19364] [4.0 Regression] embedded sparc does not bootstrap
Date: Thu, 20 Jan 2005 15:24:00 -0000 [thread overview]
Message-ID: <20050120152416.3618.qmail@sourceware.org> (raw)
In-Reply-To: <20050110151452.19364.joel@gcc.gnu.org>
------- Additional Comments From ebotcazou at gcc dot gnu dot org 2005-01-20 15:24 -------
> The bug repport was posted or a fix? This PR covered both sparc-elf and
> sparc-rtems* since I verified when I reported it that both were broken.
Bug report and fix, but the fix was to link sol2-c.c in.
> I would rather have a thin sparc-rtems configuration wrapping sparc-elf, so I
> won't commit it if you can fix both targets quickly. Make sure unix is not
> part of the cpp predefines on sparc-elf and sparc-rtems when you do, please.
Sure. I'll post it to gcc-patches and CC the interested parties so that they
could comment, before commiting it.
[About LINK_GCC_C_SEQUENCE_SPEC]
> I don't know which target needs this but if it is important to them,
> we can override it in rtemself.h. But I wanted to you watch this one
> as you fix sparc-elf/rtems.
It comes from: http://gcc.gnu.org/ml/gcc-patches/2002-04/msg00176.html
The V7 variant of libgcc/_muldi3.o has a dependency on .umul (and _divdi3.o on
.udiv) which are provided by the libc because V7 doesn't have the instructions.
So we need the double group-inclusion of "%G %L" by default, unless the linker
is smarter (like on Linux).
> Probably, "%G %L %G %L" also is SunOS/Solaris specific and actually does not
> belong into sparc.h. Also, I fail to understand how "LINK_GCC_C_SEQUENCE_SPEC"
> can be target-cpu specific. It is target-os specific.
It is actually ABI-specific. I think the V7 ABI more or less mandates it.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19364
next prev parent reply other threads:[~2005-01-20 15:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 15:15 [Bug bootstrap/19364] New: " joel at gcc dot gnu dot org
2005-01-10 15:20 ` [Bug bootstrap/19364] [4.0 Regression] " pinskia at gcc dot gnu dot org
2005-01-10 15:32 ` ebotcazou at gcc dot gnu dot org
2005-01-10 16:29 ` joel at gcc dot gnu dot org
2005-01-10 16:54 ` ebotcazou at gcc dot gnu dot org
2005-01-10 22:33 ` joel at gcc dot gnu dot org
2005-01-10 23:01 ` ebotcazou at gcc dot gnu dot org
2005-01-11 10:35 ` jakub at gcc dot gnu dot org
2005-01-12 0:03 ` joel at gcc dot gnu dot org
2005-01-20 9:52 ` ebotcazou at gcc dot gnu dot org
2005-01-20 9:56 ` ebotcazou at gcc dot gnu dot org
2005-01-20 12:42 ` joel at gcc dot gnu dot org
2005-01-20 13:34 ` corsepiu at gcc dot gnu dot org
2005-01-20 14:18 ` joel at gcc dot gnu dot org
2005-01-20 15:24 ` ebotcazou at gcc dot gnu dot org [this message]
2005-01-20 15:32 ` ebotcazou at gcc dot gnu dot org
2005-01-20 16:12 ` corsepiu at gcc dot gnu dot org
2005-01-24 0:20 ` pinskia at gcc dot gnu dot org
2005-01-24 21:32 ` cvs-commit at gcc dot gnu dot org
2005-01-24 21:35 ` ebotcazou at gcc dot gnu dot org
2005-01-24 21:40 ` pinskia at gcc dot gnu dot org
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=20050120152416.3618.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).