This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: C++ Warnings on trunk

From: "Kaveh Ghazi" <kghazi at mekamail dot com>
To: "NightStrike" <nightstrike at gmail dot com>, "Ian Lance Taylor" <iant at google dot com>
Cc: "Kai Tietz" <ktietz70 at googlemail dot com>, "Kai Tietz" <Kai dot Tietz at onevision dot com>, <gcc at gcc dot gnu dot org>
Date: Tue, 8 Jul 2008 12:09:01 -0700
Subject: Re: C++ Warnings on trunk
References: <b609cb3b0807080932w38b4fc7ft99fcf02b6a734aa5@mail.gmail.com><m3myksxqv1.fsf@google.com><b609cb3b0807081000o2c5c9b90k4742b133dbda3e6@mail.gmail.com> <m3bq18xpus.fsf@google.com>

From: "Ian Lance Taylor" <iant@google.com>

Kaveh mentioned these in his original e-mail, explained why he found
it difficult to fix, and added this to the Makefile so that it
wouldn't break the build.

# bitmap.c contains -Wc++compat warnings.
bitmap.o-warn = -Wno-error

This too should be fixed soon but need not be fixed immediately.
Ian


Right, here's the original link where I mention it:
http://gcc.gnu.org/ml/gcc-patches/2008-06/msg01658.html

This involves a cast from one type to another through a void*. I haven't been able to convince myself that this is completely safe. If someone understands why the code is violating type-safety intentionally and can explain why it's always safe, I would be happy to insert the appropriate cast and fix it.

Follow-Ups:
- Re: C++ Warnings on trunk
  - From: Andreas Schwab

References:
- C++ Warnings on trunk
  - From: NightStrike
- Re: C++ Warnings on trunk
  - From: Ian Lance Taylor
- Re: C++ Warnings on trunk
  - From: NightStrike
- Re: C++ Warnings on trunk
  - From: Ian Lance Taylor

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]