Re: [AD] Fixing a pair of trivial warnings in Allegro 4.4

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]


Thanks, applied. The best way to send patches these days is through github.

I'd prefer to fix the aliasing bugs, rather than disabling the aliasing optimizations, but if that's not possible, it'd be ok by me to add that flag.

-SL

On 09/01/2015 01:46 PM, Boon947 wrote:
Hello,

I've posted this patch to the forums, but the discussion seems
to have died down. Is the mailing list a better place to discuss
patches?

The attached patch fixes a pair of trivial warnings in Allegro 4.4

I also noticed a warning about an aliasing problem in the OSS code;
with compilers becoming more aggressive at high optimization levels,
it might be prudent to add -fno-strict-aliasing to the CFLAGS, as
Linux has been doing for ages.

Regards.

(Please CC me in replies)



_______________________________________________
Allegro-developers mailing list
Allegro-developers@xxxxxxxxxx
https://mail.gna.org/listinfo/allegro-developers





Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/