From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: zack@codesourcery.com
Cc: gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: Add new target: vxworks for xscale
Date: Sat, 10 May 2003 17:35:00 -0000 [thread overview]
Message-ID: <10305101739.AA24075@vlsi1.ultra.nyu.edu> (raw)
Given what you have said, and given how very broken the patch was, I
can only conclude you did not test it beyond "yup, it compiles." For
instance, any program that used exception handling would have gotten
loader errors when actually run on VxWorks.
No, I didn't test it, instead taking it for granted that the submitter did.
I only test patches to make sure they don't break mainline targets, assuming
that the submitter verified they do as they are supposed to. Indeed I'm
quite surprised it worked on his configuration but not on yours.
It was partly your comment about loader errors that motivated me to get
Olivier involved since it seems like there are different configurations
involved.
next reply other threads:[~2003-05-10 17:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 17:35 Richard Kenner [this message]
2003-05-10 17:49 ` Zack Weinberg
2003-05-10 21:10 ` Olivier Hainque
2003-05-10 23:09 ` Zack Weinberg
2003-05-11 10:14 ` Olivier Hainque
2003-05-12 18:57 ` Zack Weinberg
2003-05-13 13:30 ` Olivier Hainque
-- strict thread matches above, loose matches on Subject: below --
2003-05-10 21:21 Richard Kenner
2003-05-10 18:12 Richard Kenner
2003-05-10 14:54 Richard Kenner
2003-05-10 17:14 ` Zack Weinberg
2003-05-10 14:49 Richard Kenner
2003-05-10 12:22 Richard Kenner
2003-05-10 13:00 ` Toon Moene
2003-05-10 13:09 ` Joseph S. Myers
2003-05-10 14:56 ` Daniel Jacobowitz
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=10305101739.AA24075@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=zack@codesourcery.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).