public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: David Korn <dkorn@pixelpower.com>
To: "'koh@knapp.com'" <koh@knapp.com>, Hua Ji <hji@netscreen.com>
Cc: crossgcc@sources.redhat.com
Subject: RE: gcc compile
Date: Sun, 01 Apr 2001 00:00:00 -0000	[thread overview]
Message-ID: <718D38CAB6E0D011B2C90060970C28A56425EF@EXCHANGESERVER> (raw)
Message-ID: <20010401000000.ZQMI5euaq90E_usL_t9fioo2indFrXLKKGyXjzq6ViM@z> (raw)

>-----Original Message-----
>From: Helmut Kolb [ mailto:Helmut.Kolb@knapp.com ]

>I am unable to find such a think (which sounds nice) in my version of
>gcc, which i compiled for i960 about a year ago:
>,----------------------------- [ gcc -v ] -----------------------------
>| Reading specs from
>| /usr/local/i960/compiler/lib/gcc-lib/i960-unknown-coff/2.95.2/specs
>| gcc version 2.95.2 19991024 (release)
>`----------------------------------------------------------------------
>2.92.2 shoudn't be sooo old - right?
>
>Is the "sim" option a new feature, a special patch, or something enabled
>for some special cpus?

  Yep.  Sorry, but it's for powerpc only.  The GDB debugger comes with a 
ppc simulator, and the -sim flag compiles code to run with it.  There aren't
simulators for any other cpus.  This is from the "IBM RS/6000 and PowerPC
Options" section of the manual:

----------snip!--------------
-msim 
On embedded PowerPC systems, assume that the startup module is called
`sim-crt0.o' and the standard C libraries are `libsim.a' and `libc.a'. This
is default for `powerpc-*-eabisim' configurations. 
----------snip!--------------

       DaveK
-- 
The Boulder Pledge: "Under no circumstances will I ever purchase anything 
offered to me as the result of an unsolicited email message. Nor will I 
forward chain letters, petitions, mass mailings, or virus warnings to large 
numbers of others. This is my contribution to the survival of the online
community."


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

             reply	other threads:[~2001-04-01  0:00 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-19  1:56 David Korn [this message]
2001-04-01  0:00 ` David Korn
  -- strict thread matches above, loose matches on Subject: below --
2001-01-23  9:21 Jens-Christian Lache
2001-01-23  9:29 ` Philip Blundell
2001-04-01  0:00   ` Philip Blundell
2001-04-01  0:00 ` Jens-Christian Lache
2001-01-22  7:08 Yves Rutschle
2001-04-01  0:00 ` Yves Rutschle
2001-01-22  4:27 Yves Rutschle
2001-01-22  4:41 ` Jens-Christian Lache
2001-04-01  0:00   ` Jens-Christian Lache
2001-01-22 13:38 ` Philip Blundell
2001-01-23  2:18   ` Richard Earnshaw
2001-01-23  2:26     ` Philip Blundell
2001-04-01  0:00       ` Philip Blundell
2001-04-01  0:00     ` Richard Earnshaw
2001-04-01  0:00   ` Philip Blundell
2001-04-01  0:00 ` Yves Rutschle
2001-01-22  3:45 Yves Rutschle
2001-01-22  3:58 ` Jens-Christian Lache
2001-04-01  0:00   ` Jens-Christian Lache
2001-01-22  4:07 ` Jens-Christian Lache
2001-04-01  0:00   ` Jens-Christian Lache
2001-01-22  4:37 ` Jens-Christian Lache
2001-04-01  0:00   ` Jens-Christian Lache
2001-04-01  0:00 ` Yves Rutschle
     [not found] <718D38CAB6E0D011B2C90060970C28A56425F0@EXCHANGESERVER>
2001-01-19  2:49 ` Jens-Christian Lache
2001-04-01  0:00   ` Jens-Christian Lache
2001-01-19  2:29 David Korn
2001-01-20  9:51 ` Philip Blundell
2001-01-20 17:15   ` David Feustel
2001-01-21  1:51     ` Philip Blundell
2001-04-01  0:00       ` Philip Blundell
2001-04-01  0:00     ` David Feustel
2001-01-22  2:53   ` Jens-Christian Lache
2001-01-22  3:08     ` Philip Blundell
2001-01-22  7:00       ` Jens-Christian Lache
2001-04-01  0:00         ` Jens-Christian Lache
2001-04-01  0:00       ` Philip Blundell
2001-01-22  3:22     ` Richard Earnshaw
2001-04-01  0:00       ` Richard Earnshaw
2001-04-01  0:00     ` Jens-Christian Lache
2001-04-01  0:00   ` Philip Blundell
2001-04-01  0:00 ` David Korn
2001-01-19  2:21 Jens-Christian Lache
2001-01-19  2:58 ` Pierre Saucourt-Harmel (r54698)
2001-04-01  0:00   ` Pierre Saucourt-Harmel (r54698)
2001-04-01  0:00 ` Jens-Christian Lache
2001-01-18 15:43 Hua Ji
2001-01-18 22:35 ` Helmut Kolb
2001-01-19  3:13   ` Kai Ruottu
2001-04-01  0:00     ` Kai Ruottu
2001-04-01  0:00   ` Helmut Kolb
2001-04-01  0:00 ` Hua Ji
2001-01-18  9:27 Sascha Andres
2001-01-18 13:39 ` Jonathan Larmour
2001-04-01  0:00   ` Jonathan Larmour
2001-01-18 15:23 ` Gerrit Peter Haase
2001-01-22  0:19   ` Sascha Andres
2001-01-22  2:43     ` Jens-Christian Lache
2001-04-01  0:00       ` Jens-Christian Lache
2001-04-01  0:00     ` Sascha Andres
2001-04-01  0:00   ` Gerrit Peter Haase
2001-04-01  0:00 ` Sascha Andres

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=718D38CAB6E0D011B2C90060970C28A56425EF@EXCHANGESERVER \
    --to=dkorn@pixelpower.com \
    --cc=crossgcc@sources.redhat.com \
    --cc=hji@netscreen.com \
    --cc=koh@knapp.com \
    /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).