Tcl Source Code

View Ticket
Login
Ticket UUID: 918871
Title: -Wno-strict-aliasing woes
Type: Bug Version: obsolete: 8.5a1
Submitter: dgp Created on: 2004-03-18 16:32:35
Subsystem: 53. Configuration and Build Tools Assigned To: rmax
Priority: 6 Severity:
Status: Closed Last Modified: 2004-11-12 03:21:27
Resolution: Fixed Closed By: hobbs
    Closed on: 2004-11-11 20:21:27
Description:
None of
   gcc version egcs-2.91.66 (egcs-1.1.2 release)
   gcc version 2.95.3
   gcc version 3.2.3
will tolerate the new -Wno-strict-aliasing option.

They all currently fail to compile the HEAD.

Change the option to -fno-strict-aliasing
(which rmax claims is preferred) and all
of them are happy again.
User Comments: hobbs added on 2004-11-12 03:21:27:
Logged In: YES 
user_id=72656

As new code is added, this is constantly something to watch
for.  I'm closing this to allow other specific reports to be
opened.

dgp added on 2004-09-09 21:44:40:
Logged In: YES 
user_id=80530

status?

hobbs added on 2004-07-20 07:15:16:
Logged In: YES 
user_id=72656

this has been applied to Tcl/Tk-8.4 and Tk-8.5.  Tcl 8.5 was
type-pune safe, but some new changes in Tcl 8.5 need more
corrections.

dgp added on 2004-03-20 02:17:35:
Logged In: YES 
user_id=80530


rmax can close this when he's
satisfied the HEAD is working again.

rmax added on 2004-03-19 01:39:00:

File Added - 80563: gcc3.3-strict-aliasing.patch

Logged In: YES 
user_id=124643

The attached patch fixes the 11 warnings I got when I
compiled HEAD with gcc-3.3.3 today.
8 of them were related to TclpTime_t which is unneeded and
will be removed by this patch. The other three warnings are
being worked around by using temporary pointers instead of
passing addresses to the respective functions directly. I
guess, that most optimizers are able eliminate this
temporaries, so it won't affect performance, but they are
not in performance-critical sections anyways.

Attachments: