public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: lium@i-net.com.cn To: gcc-gnats@gcc.gnu.org Subject: c/7650: gcc generate a wrong code Date: Tue, 20 Aug 2002 07:36:00 -0000 [thread overview] Message-ID: <20020820140857.4255.qmail@sources.redhat.com> (raw) >Number: 7650 >Category: c >Synopsis: gcc generate a wrong code >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Tue Aug 20 07:16:04 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Start Network, inc. >Release: gcc v3.0 >Organization: >Environment: cygwin >Description: * * hi, * i'm a programmer for a embedded system project, * i am using the gcc as the compiler. my host is x86, and target machine * is ARM. * the follwing is my bug report. would you tell me is it a bug, and if it * was a bug, how can i avoid facing it. * thanks in advanced. * * GCC BUG REPORT * when i complid the following source code, * the gcc complier will generate a big bug, * which may cause the local variable len get a invalid value. * it is terrible for me. * i found it when i disassemble the obj file. * So, you can disamble the .o file and you will touch the bug. >How-To-Repeat: see the attached file's comment >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-08-20 14:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-20 7:36 lium [this message] 2002-10-25 15:33 jbuck
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=20020820140857.4255.qmail@sources.redhat.com \ --to=lium@i-net.com.cn \ --cc=gcc-gnats@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: linkBe 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).