From mint-bounce@lists.fishpool.fi Wed Apr 21 05:40:30 2010 MIME-Version: 1.0 X-Mailer: AfterLogic WebMail Pro PHP X-Originating-IP: 78.32.119.240 X-Priority: 3 (Normal) Message-ID: From: p.slegg@scubadivers.co.uk Cc: mint@lists.fishpool.fi Subject: Re: [MiNT] GCC 4.5.0 Date: Wed, 21 Apr 2010 10:36:00 +0100 (BST) Content-Type: text/plain; charset="utf-8" X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: p.slegg@scubadivers.co.uk Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from Quoted-Printable to 8bit by mail.sparemint.org id o3L9eUD7012184 For those, like me, who have no idea what mudflap is: http://www.stlinux.com/devel/debug/mudflap It seems it is an attempt to fix some of the horrible things that C can do but it really shouldn't be able to do. :-) "locking the stable door after the horse has bolted" springs to mind. Peter >---- Original Message ---- >From: Vincent Rivière >To: mint@lists.fishpool.fi >Sent: Tue, Apr 20, 2010, 9:58 PM >Subject: Re: [MiNT] GCC 4.5.0 > >Le 20/04/2010 20:50, Eero Tamminen a écrit : >> What happens if one uses them to compile MiNT kernel itself >> (besides things slowing down a lot with mudflap)? :-) > >Hmmm... Probably bad things, as the libc is used at least to display >messages, and mudflap use wrappers around libc functions... >But this should be tried. We could ask somewhere if it is possible to use >these features with the Linux kernel, the problem is probably similar. > >-- >Vincent Rivière