public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: jiayu 33576 <jiayu@huawei.com>
To: Eljay Love-Jensen <eljay@adobe.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Two additional errors of GCC 2.96
Date: Sun, 22 Aug 2004 04:50:00 -0000	[thread overview]
Message-ID: <1329d1121e.1121e1329d@huawei.com> (raw)

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


The Gcc 2.96 is provided by WindRiver with it's tool Tornado, which is GUI tool for vxworks. I don't how the version number 2.96 come from. It's just the result of "gcc -v". I have contact with Wind River. I am not very familiar with gcc. Is it easy to change my gcc to 3.3.4? Does it perform just like the one provided by WindRiver?
Thanks a lot!

name:   jiayu 
email:   jiayu@huawei.com

**************************************************************
This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
**************************************************************

----- Original Message -----
From: Eljay Love-Jensen <eljay@adobe.com>
Date: Saturday, August 21, 2004 7:52 pm
Subject: Re: Two additional errors of GCC 2.96

> Jiayu,
> 
> I recommend upgrading to the most current version of GCC.  Either 
> GCC 3.4.1 
> (latest and greatest), or GCC 3.3.4 (yesterday's tried and true).
> 
> There is no "GCC 2.96".  It's an unofficial, maverick release of 
> GCC by Red 
> Hat.  It's not supported on this forum (although we do give some 
> general 
> advice).
> 
> Your code snippets are incomplete.
> 
> Is your enum supposed to be missing the terminating semicolon (and 
> thus 
> typedefing to VOS_UINT16)?  If so,  have you tried separating out 
> g_uwLogicalBoardNo variable from the typedef?
> 
> Is your VOS_NULL_WORD define supposed to come AFTER it is being used?
> 
> Is your typedef of VOS_UINT16 supposed to come AFTER it is being used?
> 
> For your "compiler can't assign by structure"...
> 
> Is there a good reason to override the platform recommended 
> packing, which 
> can cause errors such as "Internal compiler error in 
> 'move_by_pieces'"?
> HTH,
> --Eljay
> 
> 

[-- Attachment #2: Card for jiayu 33576 <jiayu@huawei.com> --]
[-- Type: text/x-vcard, Size: 86 bytes --]

begin:vcard
n:Jia;Yu
fn:Jia Yu
version:2.1
email;internet:jiayu@huawei.com
end:vcard


             reply	other threads:[~2004-08-21 16:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-22  4:50 jiayu 33576 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-21 11:52 jiayu 33576
2004-08-21 19:28 ` Eljay Love-Jensen
2004-08-24  5:23 ` Iain Woolf

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=1329d1121e.1121e1329d@huawei.com \
    --to=jiayu@huawei.com \
    --cc=eljay@adobe.com \
    --cc=gcc-help@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).