From: Joe Buck <Joe.Buck@synopsys.COM>
To: Fengwei Yin <yfw.debian@gmail.com>
Cc: gcc <gcc@gcc.gnu.org>
Subject: Re: Problem about gcc 4.1 + binutil 2.16.92 + glibc 2.4 + ARM EABI
Date: Thu, 01 Jun 2006 01:38:00 -0000 [thread overview]
Message-ID: <20060601013803.GR9428@synopsys.com> (raw)
In-Reply-To: <c4b2dcca0605311829i5d5dd37evb134eadf181d23e1@mail.gmail.com>
On Thu, Jun 01, 2006 at 09:29:08AM +0800, Fengwei Yin wrote:
> Hi Richard,
> Thanks for your information. I will ask for help on gcc-help@gcc.gnu.org.
OK, great.
> But I still have question about gcc here:
Um, you're still here? Please don't ask more questions here.
Your questions reveal that you are a beginning C programmer with
fundamental misunderstandings about the language. It's not appropriate to
take up time on the compiler developers' list so people take time away
from developing the compiler to teach you the C language.
prev parent reply other threads:[~2006-06-01 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 6:59 Fengwei Yin
2006-05-31 9:23 ` Richard Earnshaw
2006-06-01 1:29 ` Fengwei Yin
2006-06-01 1:38 ` Joe Buck [this message]
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=20060601013803.GR9428@synopsys.com \
--to=joe.buck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=yfw.debian@gmail.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).