public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcj/25187] New: dereferencing type-punned pointer warnings while building libgcj Date: Wed, 30 Nov 2005 18:53:00 -0000 [thread overview] Message-ID: <bug-25187-6528@http.gcc.gnu.org/bugzilla/> (raw) /home/pinskia/src/newtest/trunk/libjava/java/lang/Class.h: In member function 'java::lang::Class* java::lang::Class::getComponentType()': /home/pinskia/src/newtest/trunk/libjava/java/lang/Class.h:339: warning: dereferencing type-punned pointer will break strict-aliasing rules /home/pinskia/src/newtest/trunk/libjava/prims.cc: In function 'void catch_segv(int)': /home/pinskia/src/newtest/trunk/libjava/prims.cc:149: warning: dereferencing type-punned pointer will break strict-aliasing rules /home/pinskia/src/newtest/trunk/libjava/prims.cc: In function 'void catch_fpe(int)': /home/pinskia/src/newtest/trunk/libjava/prims.cc:161: warning: dereferencing type-punned pointer will break strict-aliasing rules /home/pinskia/src/newtest/trunk/libjava/jni.cc: In function 'jint _Jv_JNI_DestroyJavaVM(JavaVM*)': /home/pinskia/src/newtest/trunk/libjava/jni.cc:2440: warning: dereferencing type-punned pointer will break strict-aliasing rules /home/pinskia/src/newtest/trunk/libjava/interpret.cc: In static member function 'static void _Jv_InterpMethod::run(void*, ffi_raw*, _Jv_InterpMethod*)': /home/pinskia/src/newtest/trunk/libjava/interpret.cc:808: warning: dereferencing type-punned pointer will break strict-aliasing rules /home/pinskia/src/newtest/trunk/libjava/gnu/gcj/io/natSimpleSHSStream.cc: In static member function 'static JArray<__java_byte>* gnu::gcj::io::SimpleSHSStream::shsFinal(JArray<__java_byte>*)': /home/pinskia/src/newtest/trunk/libjava/gnu/gcj/io/natSimpleSHSStream.cc:32: warning: dereferencing type-punned pointer will break strict-aliasing rules I have not looked to see if these are false postives at all. -- Summary: dereferencing type-punned pointer warnings while building libgcj Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgcj AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pinskia at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25187
next reply other threads:[~2005-11-30 18:53 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-11-30 18:53 pinskia at gcc dot gnu dot org [this message] 2005-11-30 18:55 ` [Bug libgcj/25187] " pinskia at gcc dot gnu dot org 2005-11-30 20:35 ` rguenth at gcc dot gnu dot org 2006-02-09 1:35 ` bryce at gcc dot gnu dot org 2006-02-09 1:38 ` mckinlay at redhat 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-25187-6528@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: 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).