From: "Rask Ingemann Lambertsen" <rask@kampsax.k-net.dk>
To: "GCC mailing list" <gcc@gcc.gnu.org>
Subject: Re: MIPS16 -mentry pseudo instruction definitions
Date: Thu, 30 Sep 1999 18:02:00 -0000 [thread overview]
Message-ID: <770.925T466T9792898@kampsax.k-net.dk> (raw)
Message-ID: <19990930180200.wmjzD-3J9TkoWPilUHtQIgWfT77K5my1PgZouT5nduw@z> (raw)
In-Reply-To: <19990913125633.17782.rocketmail@web601.yahoomail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]
Den 13-Sep-99 13:56:33 skrev Andre McCurdy følgende om "Re: MIPS16 -mentry pseudo instruction definitions":
> Is there any way of tracking down when the -mentry
> option became part of gcc (and where the code come
> from) ?
Yes, the Changelog files and "cvs log file1 [file2 ...]" ought to do the
trick.
Regards,
/¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯T¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯\
| Rask Ingemann Lambertsen | E-mail: mailto:rask@kampsax.k-net.dk |
| Registered Phase5 developer | WWW: http://www.gbar.dtu.dk/~c948374/ |
| A4000, 866 kkeys/s (RC5-64) | "ThrustMe" on XPilot, ARCnet and IRC |
| It is my tag line - I stole it first! |
next prev parent reply other threads:[~1999-09-30 18:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-13 5:53 Andre McCurdy
1999-09-13 8:52 ` Rask Ingemann Lambertsen [this message]
1999-09-30 18:02 ` Rask Ingemann Lambertsen
1999-09-13 12:32 ` Jim Wilson
1999-09-30 18:02 ` Jim Wilson
1999-09-30 18:02 ` Andre McCurdy
-- strict thread matches above, loose matches on Subject: below --
1999-09-14 7:07 Andre McCurdy
1999-09-30 18:02 ` Andre McCurdy
1999-09-10 8:21 Andre McCurdy
1999-09-10 11:57 ` Jim Wilson
1999-09-30 18:02 ` Jim Wilson
1999-09-30 18:02 ` Andre McCurdy
1999-09-09 7:06 Andre McCurdy
1999-09-09 14:42 ` Richard Henderson
1999-09-30 18:02 ` Richard Henderson
1999-09-30 18:02 ` Andre McCurdy
1999-09-08 11:33 Andre McCurdy
1999-09-08 14:05 ` Jeffrey A Law
1999-09-30 18:02 ` Jeffrey A Law
1999-09-30 18:02 ` Andre McCurdy
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=770.925T466T9792898@kampsax.k-net.dk \
--to=rask@kampsax.k-net.dk \
--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).