public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: mmitchel@qualcomm.com To: gcc-gnats@gcc.gnu.org Subject: c/6873: Improper Alignment Parameters Emitted by Compiler for .comm Section Date: Thu, 30 May 2002 13:36:00 -0000 [thread overview] Message-ID: <20020530202430.27671.qmail@sources.redhat.com> (raw) >Number: 6873 >Category: c >Synopsis: Improper Alignment Parameters Emitted by Compiler for .comm Section >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu May 30 13:26:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: mmitchel@qualcomm.com >Release: gcc version 3.1 arm-elf >Organization: >Environment: cross compile, windows nt, cygwin $ arm-elf-gcc -v Reading specs from /gnude/lib/gcc-lib/arm-elf/3.1/specs Configured with: ../src/configure --target=arm-elf --host=i686-pc-cygwin --prefi x=/gnude --with-local-prefix=/gnude/local --with-gnu-as --with-gnu-ld Thread model: single gcc version 3.1 >Description: The compiler not emitting correct assembly output for following example: $ more test.c int i; int j; $ arm-elf-gcc -S test.c $ more test.s .file "test.c" .comm i, 4, 32 .comm j, 4, 32 .ident "GCC: (GNU) 3.1" the third paramater, alignment parameter, to the .comm pseudo op is incorrect. Incorrect output impacts memory use and requirements of generating small code for embedded targets. >How-To-Repeat: >Fix: In the file gcc\config\arm\elf.h, at line 172, scale the parameter ALIGN by dividing by BITS_PER_UNIT. This is how this macro is implemented for other targets; this may be an undesired omission for this target. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-05-30 20:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-30 13:36 mmitchel [this message] 2003-05-10 23:46 Dara Hazeghi 2003-05-12 10:45 steven
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=20020530202430.27671.qmail@sources.redhat.com \ --to=mmitchel@qualcomm.com \ --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).