[Bug objc++/16816] obj-c++ parser error with multi-colon selectors
-- What|Removed |Added AssignedTo|unassigned at gcc dot gnu |zlaski at apple dot com |dot org | Status|NEW |ASSIGNED Last reconfirmed|2005-07-02 02:14:23 |2005-07-02 02:52:31 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16816
[Bug objc/22274] [4.1 Regression] string[1-4].m, const-str-5.m fails with the gnu runtime
-- What|Removed |Added AssignedTo|unassigned at gcc dot gnu |zlaski at apple dot com |dot org | Status|NEW |ASSIGNED Last reconfirmed|2005-07-05 00:40:13 |2005-07-06 21:11:49 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22274
[Bug objc/22274] [4.1 Regression] string[1-4].m, const-str-5.m fails with the gnu runtime
--- Additional Comments From zlaski at apple dot com 2005-07-07 06:33 --- Fixed for 4.1. -- What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22274
[Bug c++/21349] New: Spurious '$' in warning messages
Compile the source code pasted below with "-Os -Wuninitialized" using C++. You
should get the
following warnings:
uninit.cpp: In function 'int foo()':
uninit.cpp:13: warning: 'range$begin' is used uninitialized in this function
uninit.cpp: In function 'int bar()':
uninit.cpp:21: warning: 'range$end' may be used uninitialized in this function
where the '.' has been secretly replaced by '$'. This used to be a problem
with C and ObjC in the past
also, but appears fixed now.
uninit.cpp ==
/* Contributed by Ziemowit Laski <[EMAIL PROTECTED]> */
/* Check that unused warnings triggered by the optimizer contain '.' rather
than '$' in them. */
/* { dg-do compile } */
/* { dg-options "-Os -Wuninitialized" } */
typedef struct Range {
long begin, end;
} Range;
int foo(void) {
Range range;
while(range.begin != 0) { } /* { dg-warning ".range\\.begin. is used
uninitialized in this function" } */
return 0;
}
extern int baz(void);
int bar(void) {
Range range; /* { dg-warning ".range\\.end. may be used uninitialized in
this function" } */
do {
if(baz()) range.end = 2;
}
while(range.end != 0);
return 0;
}
--
Summary: Spurious '$' in warning messages
Product: gcc
Version: 4.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: zlaski at apple dot com
CC: gcc-bugs at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21349
[Bug objc/18971] [4.0 Regression] Can't send messages to methods with arrays as parameters
-- What|Removed |Added AssignedTo|unassigned at gcc dot gnu |zlaski at apple dot com |dot org | Status|NEW |ASSIGNED Last reconfirmed|2004-12-14 00:16:29 |2004-12-23 22:11:14 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18971
[Bug objc/19321] [4.0 regression] objc ignores volatile in argument types for messages
--- Additional Comments From zlaski at apple dot com 2005-01-07 23:11 --- I'll take this; there is also a problem with encoding 'const' parameters, already fixed in apple-ppc- branch. I'll tackle the const and volatile issue together. -- What|Removed |Added AssignedTo|unassigned at gcc dot gnu |zlaski at apple dot com |dot org | Status|NEW |ASSIGNED Last reconfirmed|2005-01-07 23:01:19 |2005-01-07 23:11:14 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19321
[Bug objc/19321] [4.0 regression] objc ignores volatile in argument types for messages
--- Additional Comments From zlaski at apple dot com 2005-01-10 19:43 --- Ok, I was wrong. :-) The bug described herein is unrelated to the const encoding issue. What is more, I'm dumbfounded as to how the anomaly comes to be. Stepping through objc_start_function() and friends, one can see that the volatile-ness of the argument is preserved all the way through. I did notice some discrepancies between how ObjC synthesizes C functions vs. how such functions get constructed in C itself, and have created a patch to minimize them. Alas, this does not fix the problem. :-( -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19321
[Bug objc/19321] [4.0 regression] objc ignores volatile in argument types for messages
-- What|Removed |Added AssignedTo|zlaski at apple dot com |pinskia at gcc dot gnu dot ||org Severity|critical|normal Priority|P2 |P3 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19321
[Bug objc/19321] [4.0 regression] objc ignores volatile in argument types for messages
--- Additional Comments From zlaski at apple dot com 2005-01-10 20:23 --- Alas, comment #1 is a non-starter for ObjC++ reasons, plus it is factually wrong (since we _do_ preserve the volatile on the function argument, which is why this is mysterious). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19321
[Bug objc/19321] [4.0 regression] objc ignores volatile in argument types for messages
-- What|Removed |Added AssignedTo|unassigned at gcc dot gnu |zlaski at apple dot com |dot org | Status|NEW |ASSIGNED Last reconfirmed|2005-01-07 23:11:14 |2005-01-15 02:20:09 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19321
[Bug objc/19321] [4.0 regression] objc ignores volatile in argument types for messages
--- Additional Comments From zlaski at apple dot com 2005-01-15 21:27 --- Committed fix. -- What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19321
[Bug objc/18408] [4.0 Regression] ICE compiling code that involves casting classes
--- Additional Comments From zlaski at apple dot com 2005-01-20 21:48 --- Of course, for this particular bug, someone could just review the patch that I posted two months ago... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18408
[Bug objc/18408] [4.0 Regression] ICE compiling code that involves casting classes
--- Additional Comments From zlaski at apple dot com 2004-11-09 23:34 --- I'll take a look. -- What|Removed |Added Status|NEW |ASSIGNED Last reconfirmed|2004-11-09 23:16:51 |2004-11-09 23:34:24 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18408
[Bug objc/18408] [4.0 Regression] ICE compiling code that involves casting classes
--- Additional Comments From zlaski at apple dot com 2004-11-12 01:36 --- Patch posted here: http://gcc.gnu.org/ml/gcc-patches/2004-11/msg00925.html Awaiting feedback. -- What|Removed |Added Status|ASSIGNED|WAITING http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18408
