Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: imzhuli at vip dot qq.com
Target Milestone: ---
Created attachment 47627
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47627&action=edit
source codes (DList.h
NCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: imzhuli at vip dot qq.com
Created attachment 30878
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30878&action=edit
test case.
pls refer to the a
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50282
Bug #: 50282
Summary: pointer-to-member cast works incorrectly
Classification: Unclassified
Product: gcc
Version: 4.1.2
Status: UNCONFIRMED
Severity: critical
Priorit
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50282
zhuli changed:
What|Removed |Added
Severity|critical|major
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50282
--- Comment #2 from zhuli 2011-09-03 11:31:57 UTC
---
I've never used any unint32_t tu hold any pointer-to-member,
I just tested and find out the sizeof (pointer-to-member-function) is 16,
then i used a pointer-to-uint32_t four times to dump th
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50282
--- Comment #4 from zhuli 2011-09-03 12:17:35 UTC
---
yes, you are right.
As an addition, compiling with -O2 might yield an warning, as you metioned.
but i checked my env(32-bit) and used default compiler option, so i just simply
assumed 4byte-
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50282
--- Comment #6 from zhuli 2011-09-05 03:12:55 UTC
---
I guess we have some agreement on HOW gcc works. the following are what i got
through the test-cases:
1.simply using &T4::f, will only get a value of T2::f, as the function f
accessed through
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53762
Bug #: 53762
Summary: pointer-casts don't always check null-pointers
Classification: Unclassified
Product: gcc
Version: 4.2.1
Status: UNCONFIRMED
Severity: major
Prio