public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Panagiotis Issaris <takis@lumumba.luc.ac.be>
To: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org
Subject: c++/6235: Using -fpack-struct creats segfaulting code.
Date: Tue, 09 Apr 2002 06:46:00 -0000 [thread overview]
Message-ID: <E16uvsc-0002E4-00@ares> (raw)
>Number: 6235
>Category: c++
>Synopsis: Using -fpack-struct creats segfaulting code.
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: wrong-code
>Submitter-Id: net
>Arrival-Date: Tue Apr 09 06:46:27 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Panagiotis Issaris
>Release: 3.0.3 20011215 (Debian prerelease) (Debian testing/unstable)
>Organization:
>Environment:
System: Linux ares 2.4.17-xfs #5 Sat Mar 16 20:42:21 CET 2002 i586 unknown
Architecture: i586
host: i386-pc-linux-gnu
build: i386-pc-linux-gnu
target: i386-pc-linux-gnu
configured with: ../src/configure -v --enable-languages=c,c++,java,f77,proto,objc --prefix=/usr --infodir=/share/info --mandir=/share/man --enable-shared --with-gnu-as --with-gnu-ld --with-system-zlib --enable-long-long --enable-nls --without-included-gettext --disable-checking --enable-threads=posix --enable-java-gc=boehm --with-cpp-install-dir=bin --enable-objc-gc i386-linux
>Description:
When compiling a C++ source file with the -fpack-struct flag, code is generated which segfaults when run. When creating
a similar C source file and using the same flag, there's no problem at all. The problem only occurs if there is a struct or class in the source file, if I remove the structs and compile with the flag, it runs just fine. I tried this to rule out the possibility that it had something to do with linking in default libraries or compiling files in <string> or <iostream> which are included in the source file.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-04-09 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 6:46 Panagiotis Issaris [this message]
2002-04-09 7:52 sirl
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=E16uvsc-0002E4-00@ares \
--to=takis@lumumba.luc.ac.be \
--cc=debian-gcc@lists.debian.org \
--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: 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).