public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "michael dot haubenwallner at salomon dot at" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/30826]  New: alignment error when optimizing with inlining
Date: Fri, 16 Feb 2007 17:45:00 -0000	[thread overview]
Message-ID: <bug-30826-9385@http.gcc.gnu.org/bugzilla/> (raw)

Attached test program dumps core when built with optimization using gcc-4.1.1
on ia64-hp-hpux11.23.

It works without optimization, or when using "-O1 -fno-inline".

It is same both with HP's gcc-4.1.1 as well with self-built gcc-4.1.1, both
using GNU as.

$ /opt/hp-gcc-4.1.1/bin/gcc -v
Using built-in specs.
Target: ia64-hp-hpux11.23
Configured with: /tmp/gcc-4.1.1.tar.gz/gcc-4.1.1/configure
--host=ia64-hp-hpux11.23 --target=ia64-hp-hpux11.23 --build=ia64-hp-hpux11.23
--prefix=/opt/hp-gcc-4.1.1 --enable-languages=c,c++ --with-gnu-as
--without-gnu-ld --with-ld=/usr/ccs/bin/ld --enable-threads=posix
Thread model: posix
gcc version 4.1.1

$ /opt/hp-gcc-4.1.1/bin/gcc inline.c
$ ./a.out

$ /opt/hp-gcc-4.1.1/bin/gcc inline.c -O1
$ ./a.out
Bus error (core dumped)

$ /opt/langtools/bin/gdb a.out
HP gdb 5.6.0 for HP Itanium (32 or 64 bit) and target HP-UX 11.2x.
Copyright 1986 - 2001 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 5.6.0 (based on GDB) is covered by the
GNU General Public License. Type "show copying" to see the conditions to
change it and/or distribute copies. Type "show warranty" for warranty/support.
..(no debugging symbols found)...
(gdb) r
Starting program: /mnt/big/logins/haubi/a.out 
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...
Program received signal SIGBUS, Bus error
  si_code: 1 - BUS_ADRALN - Invalid address alignment.
0x200000007edb4130:0 in mallinfo+0x180 () from /usr/lib/hpux32/libc.so.1
(gdb) bt
#0  0x200000007edb4130:0 in mallinfo+0x180 () from /usr/lib/hpux32/libc.so.1
#1  0x40008b0:0 in main+0x30 ()
(gdb)


-- 
           Summary: alignment error when optimizing with inlining
           Product: gcc
           Version: 4.1.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: michael dot haubenwallner at salomon dot at
 GCC build triplet: ia64-hp-hpux11.23
  GCC host triplet: ia64-hp-hpux11.23
GCC target triplet: ia64-hp-hpux11.23


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30826


             reply	other threads:[~2007-02-16 17:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16 17:45 michael dot haubenwallner at salomon dot at [this message]
2007-02-16 17:50 ` [Bug tree-optimization/30826] " michael dot haubenwallner at salomon dot at
2007-02-16 17:56 ` michael dot haubenwallner at salomon dot at
2007-02-16 17:58 ` michael dot haubenwallner at salomon dot at
2007-02-16 18:06 ` michael dot haubenwallner at salomon dot at
2007-02-16 23:26 ` [Bug target/30826] " sje at cup dot hp dot com
2007-02-17 14:35 ` michael dot haubenwallner at salomon dot at
2007-02-17 15:01 ` michael dot haubenwallner at salomon dot at
2007-02-19 12:19 ` michael dot haubenwallner at salomon dot at
2007-02-20 17:06 ` sje at cup dot hp dot com
2008-01-07 18:32 ` [Bug target/30826] alignment error tom dot culliton at oracle dot com

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=bug-30826-9385@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).