Re: [Flightgear-devel] Compiler Warnings

2010-09-27 Thread James Turner
On 26 Sep 2010, at 22:09, ThorstenB wrote: Hi, there is a forum topic discussing compiler optimization to improve frame rate ( http://www.flightgear.org/forums/viewtopic.php?f=45p=96830 ). I have also tried this (and successfully improved mine... :-) ). However, I also compiled with

Re: [Flightgear-devel] Compiler Warnings

2010-09-27 Thread Durk Talsma
Hi all, As a general head-up. I'm trying to fix a couple of these warnings in the AI code right now. Most of it is just boring stuff. Ideal to fill a couple of hours on a rainy monday afternoon. Cheers, Durk On Mon, Sep 27, 2010 at 9:47 AM, James Turner zakal...@mac.com wrote: On 26 Sep

Re: [Flightgear-devel] Compiler Warnings

2010-09-27 Thread Durk Talsma
For your information, I just committed a bunch of fixes so that the AIModels subdirectory now compiles without warnings using -Wall, using gcc 4.3.2 Cheers, Durk -- Start uncovering the many advantages of virtual

Re: [Flightgear-devel] Compiler Warnings

2010-09-27 Thread Martin Spott
James Turner wrote: The SSE math flags are a no-brainer where supported - the -march-native and -sse flags are all Apple defaults in Xcode. BTW, as far as I remember the -sse and -sse2 are on by default for GCC on AMD64 (alias x86_64). Cheers, Martin. -- Unix _IS_ user friendly -

Re: [Flightgear-devel] Compiler Warnings

2010-09-27 Thread James Turner
On 27 Sep 2010, at 17:48, Martin Spott wrote: The SSE math flags are a no-brainer where supported - the -march-native and -sse flags are all Apple defaults in Xcode. BTW, as far as I remember the -sse and -sse2 are on by default for GCC on AMD64 (alias x86_64). It would be good if

Re: [Flightgear-devel] Compiler Warnings

2010-09-27 Thread ThorstenB
On 2010-09-27, at 17:25, James Turner wrote: The SSE math flags are a no-brainer where supported - the -march-native and -sse flags are all Apple defaults in Xcode. BTW, as far as I remember the -sse and -sse2 are on by default for GCC on AMD64 (alias x86_64). It would be good if someone who

[Flightgear-devel] Autopilot key bindings and the problem of backspace

2010-09-27 Thread Stuart Buchanan
Hi All, Currently there are a number of key bindings to enable various auto-pilot modes, e.g.: Ctrl-A Altitude lock Ctrl-H Heading lock Ctrl-G Glideslope lock Ctrl-N NAV1 lock Ctrl-P Pitch hold Ctrl-S Autothrottle Ctrl-T Terrain lock Ctrl-W Wing level F6 - Heading lock Unfortunately, it is all

Re: [Flightgear-devel] Autopilot key bindings and the problem of backspace

2010-09-27 Thread willie
On 27/09/10 21:29, Stuart Buchanan wrote: Hi All, Currently there are a number of key bindings to enable various auto-pilot modes, e.g.: Ctrl-A Altitude lock Ctrl-H Heading lock Ctrl-G Glideslope lock Ctrl-N NAV1 lock Ctrl-P Pitch hold Ctrl-S Autothrottle Ctrl-T Terrain lock Ctrl-W

Re: [Flightgear-devel] Autopilot key bindings and the problem of backspace

2010-09-27 Thread Vivian Meazza
Willie wrote: On 27/09/10 21:29, Stuart Buchanan wrote: Hi All, Currently there are a number of key bindings to enable various auto-pilot modes, e.g.: Ctrl-A Altitude lock Ctrl-H Heading lock Ctrl-G Glideslope lock Ctrl-N NAV1 lock Ctrl-P Pitch hold Ctrl-S Autothrottle

Re: [Flightgear-devel] Autopilot key bindings and the problem of backspace

2010-09-27 Thread willie
On 27/09/10 22:11, willie wrote: btw the help option (?) on the Command Mode Dialog doesn't work for me, can anyone else confirm? It works OK - it just sends the help message to the console, which is not much use in full-screen mode. Willie

Re: [Flightgear-devel] Compiler Warnings = Merge Request

2010-09-27 Thread ThorstenB
Hi, I fixed the strict-aliasing issues reported by GCC 4.4.1. Affects the generic.cxx and multiplaymgr.cxx modules. I created a merge request (let me know if you preferred patches): http://gitorious.org/fg/flightgear/merge_requests/7 cheers, Thorsten

Re: [Flightgear-devel] Compiler Warnings = Merge Request

2010-09-27 Thread Csaba Halász
On Tue, Sep 28, 2010 at 12:21 AM, ThorstenB bre...@gmail.com wrote: Hi, I fixed the strict-aliasing issues reported by GCC 4.4.1. Affects the generic.cxx and multiplaymgr.cxx modules. Unfortunately the trick with the union in multiplaymgr.cxx is not standard C, as far as I know. --