From: "Paul C. Leopardi" <leopardi@bigpond.net.au>
To: gcc@gcc.gnu.org
Subject: Need help creating a small test case for g++ 4.0.0 bug
Date: Sat, 14 May 2005 06:28:00 -0000 [thread overview]
Message-ID: <200505141216.54326.leopardi@bigpond.net.au> (raw)
Hi all,
I originally posted these messages to gcc-help, but had no reply, so I am
re-posting links to them here.
I think I have found a bug in g++ 4.0.0, but need help in reporting it.
Maintainers like their bug reports to include short test cases, but I don't
know how to generate a short test case involving inlining. I discovered the
original problem by compiling GluCat ( http://glucat.sf.net ) and the
preprocessor output from a short GluCat test program contains over 66 000
lines of libstdc++, uBLAS and Glucat code.
Can anyone help, or should I just file a bug report using the huge test case?
The original posts were:
g++ 4.0.0: hash_map hangs when compiled with -O3 on AMD64
http://gcc.gnu.org/ml/gcc-help/2005-05/msg00030.html
Re: g++ 4.0.0: hash_map hangs when compiled with -O3 on AMD64
http://gcc.gnu.org/ml/gcc-help/2005-05/msg00087.html
I am particularly interested in the interference between hash_map,
-fstrict-aliasing and -finline-functions, and I wonder if it happens on
other architectures, or only on AMD64.
Best regards, Paul Leopardi
PS.
If you try compling the current GluCat 0.1.8 using g++ 4.0.0, you will need
the following patch.
diff
-u /home/leopardi/src/glucat/glucat-0.1.8/glucat/portability.h ./portability.h
--- /home/leopardi/src/glucat/glucat-0.1.8/glucat/portability.h 2004-05-10
21:28:42.000000000 +1000
+++ ./portability.h 2005-05-01 22:11:22.000000000 +1000
@@ -28,15 +28,15 @@
#define ios_base ios // scope is different for standard C++
#endif
-//***************************** workaround for ICC and G++ 3.3+
-#if defined (__ICL) || defined (__ICC) || defined (__GNUG__) && (__GNUC__ >=
3) && (__GNUC_MINOR__ >= 3)
+//***************************** workaround for ICC, G++ 3.3+, G++ 4.0+
+#if defined (__ICL) || defined (__ICC) || defined (__GNUG__) && ((__GNUC__ ==
3) && (__GNUC_MINOR__ >= 3) || (__GNUC__ == 4))
#define _GLUCAT_PRIVATE public
#else
#define _GLUCAT_PRIVATE private
#endif
//***************************** workaround for G++ 3.2 typename bug
-#if defined (__GNUG__) && (__GNUC__ >= 3) && (__GNUC_MINOR__ <= 2)
+#if defined (__GNUG__) && (__GNUC__ == 3) && (__GNUC_MINOR__ <= 2)
#define _GLUCAT_USE_STRUCT_NAME(T)
#else
#define _GLUCAT_USE_STRUCT_NAME(T) T::
next reply other threads:[~2005-05-14 2:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 6:28 Paul C. Leopardi [this message]
2005-05-14 9:04 ` Andrew Pinski
2005-05-14 9:59 ` Paul C. Leopardi
2005-05-16 17:50 ` Janis Johnson
2005-08-03 15:18 ` Paul C. Leopardi
2005-08-03 16:16 Dan Kegel
2005-08-03 16:19 ` Daniel Berlin
2005-08-28 13:51 ` Paul C. Leopardi
2005-08-03 16:31 Volker Reichelt
2005-08-04 15:15 ` Paul C. Leopardi
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=200505141216.54326.leopardi@bigpond.net.au \
--to=leopardi@bigpond.net.au \
--cc=gcc@gcc.gnu.org \
--cc=paul.leopardi@unsw.edu.au \
/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).