public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: gcc@gcc.gnu.org
Subject: Re: cross-compilation documentation
Date: Sun, 22 Jun 2003 17:56:00 -0000	[thread overview]
Message-ID: <20030622173827.GN6353@lug-owl.de> (raw)
In-Reply-To: <02F74B2F-A4D6-11D7-AD8C-000393A6D2F2@physics.uc.edu>

[-- Attachment #1: Type: text/plain, Size: 2538 bytes --]

On Sun, 2003-06-22 13:21:51 -0400, Andrew Pinski <pinskia@physics.uc.edu>
wrote in message <02F74B2F-A4D6-11D7-AD8C-000393A6D2F2@physics.uc.edu>:
> On Sunday, Jun 22, 2003, at 13:09 US/Eastern, Peter Barada wrote:
> 
> That is a bug in the config of rs6000 of gcc which should be fixed,
> I have a patch for it and there is no need for --without-libgcc:
[...]

grepping a bit, I think this is not only a problem of pcc-linux:

jbglaw@b132l-1:~/toolchain-sources/gcc/gcc/config$ find . -type f -name linux.h -exec grep -Hi -B 5 signal.h {} \;
./alpha/linux.h-
./alpha/linux.h-/* Do code reading to identify a signal frame, and set the frame
./alpha/linux.h-   state data appropriately.  See unwind-dw2.c for the structs.  */
./alpha/linux.h-
./alpha/linux.h-#ifdef IN_LIBGCC2
./alpha/linux.h:#include <signal.h>
./i386/linux.h-/* There's no sys/ucontext.h for some (all?) libc1, so no
./i386/linux.h-   signal-turned-exceptions for them.  There's also no configure-run for
./i386/linux.h-   the target, so we can't check on (e.g.) HAVE_SYS_UCONTEXT_H.  Using the
./i386/linux.h-   target libc1 macro should be enough.  */
./i386/linux.h-#ifndef USE_GNULIBC_1
./i386/linux.h:#include <signal.h>
./ia64/linux.h-
./ia64/linux.h-/* Do code reading to identify a signal frame, and set the frame
./ia64/linux.h-   state data appropriately.  See unwind-dw2.c for the structs.  */
./ia64/linux.h-
./ia64/linux.h-#ifdef IN_LIBGCC2
./ia64/linux.h:#include <signal.h>
./rs6000/linux.h-
./rs6000/linux.h-/* Do code reading to identify a signal frame, and set the frame
./rs6000/linux.h-   state data appropriately.  See unwind-dw2.c for the structs.  */
./rs6000/linux.h-
./rs6000/linux.h-#ifdef IN_LIBGCC2
./rs6000/linux.h:#include <signal.h>
./sh/linux.h-
./sh/linux.h-/* Do code reading to identify a signal frame, and set the frame
./sh/linux.h-   state data appropriately.  See unwind-dw2.c for the structs.  */
./sh/linux.h-
./sh/linux.h-#ifdef IN_LIBGCC2
./sh/linux.h:#include <signal.h>
jbglaw@b132l-1:~/toolchain-sources/gcc/gcc/config$


Iff the fix correctly fixes this behavior, it would be nice if you could
please also fix the other architectures gcc has Linux support for.

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-06-22 17:43 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18  0:36 Dan Kegel
2003-06-18 14:58 ` Joel Sherrill
2003-06-22 17:10   ` Dan Kegel
2003-06-19  0:00 ` Jim Wilson
2003-06-22 17:12   ` Dan Kegel
2003-06-22 17:19     ` Andrew Pinski
2003-06-22 17:21       ` Dan Kegel
2003-06-22 17:35       ` Peter Barada
2003-06-22 17:50         ` Andrew Pinski
2003-06-22 17:56           ` Jan-Benedict Glaw [this message]
2003-06-22 18:07           ` Zack Weinberg
2003-06-22 20:15             ` Dan Kegel
2003-06-22 20:27               ` Zack Weinberg
2003-06-22 20:36                 ` Peter Barada
2003-06-22 21:10                   ` Daniel Jacobowitz
2003-06-23  3:06                     ` Dan Kegel
2003-06-23  4:08                       ` Jan-Benedict Glaw
2003-06-23  4:22                         ` Dan Kegel
2003-06-23  9:10                     ` Peter Barada
2003-06-23 12:20                       ` Dan Kegel
2003-06-23 12:15                         ` Peter Barada
2003-06-23 12:20                           ` Dan Kegel
2003-06-23 14:14                             ` Peter Barada
2003-06-23 15:38                               ` Hans-Peter Nilsson
2003-06-23 16:04                                 ` Dan Kegel
2003-06-23 16:11                                   ` Hans-Peter Nilsson
2003-06-23 15:57                               ` Dan Kegel
2003-06-23 13:01                           ` Daniel Jacobowitz
2003-06-23 14:14                             ` Peter Barada
2003-06-23 14:50                               ` Daniel Jacobowitz
2003-06-23 14:10                       ` Daniel Jacobowitz
2003-06-22 18:41           ` Daniel Jacobowitz
2003-06-22 17:30     ` Jan-Benedict Glaw
  -- strict thread matches above, loose matches on Subject: below --
2004-05-29  6:25 Dan Kegel
2004-05-29  6:57 ` Zack Weinberg
2004-06-01 16:35   ` Dan Kegel
2004-06-01 17:38 ` Dave Korn
2004-06-01 17:45   ` Peter Barada
2003-06-22 17:43 Dara Hazeghi
2003-06-22 17:49 ` Jan-Benedict Glaw
2003-06-22 17:49 ` Andrew Pinski
2003-06-22 17:53   ` Jan-Benedict Glaw
2003-06-24  5:26     ` Jim Wilson
2003-06-22 19:36   ` Dara Hazeghi
2003-06-27 12:13     ` Gerald Pfeifer
2001-11-13 16:21 Cross-compilation documentation Joseph S. Myers

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=20030622173827.GN6353@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=gcc@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).