From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.31.244.76 with SMTP id s73mr7285030vkh.2.1468262841006; Mon, 11 Jul 2016 11:47:21 -0700 (PDT) X-Received: by 10.157.34.133 with SMTP id y5mr104708ota.4.1468262840956; Mon, 11 Jul 2016 11:47:20 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!peer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!c52no867532qte.1!news-out.google.com!d68ni4028ith.0!nntp.google.com!r1no16246790ige.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 11 Jul 2016 11:47:20 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=2601:191:8202:8510:5985:2c17:9409:aa9c; posting-account=fdRd8woAAADTIlxCu9FgvDrUK4wPzvy3 NNTP-Posting-Host: 2601:191:8202:8510:5985:2c17:9409:aa9c References: User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: GNAT GPL 2016 on Debian Jessie From: rieachus@comcast.net Injection-Date: Mon, 11 Jul 2016 18:47:20 +0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Received-Bytes: 2389 X-Received-Body-CRC: 4275837497 Xref: news.eternal-september.org comp.lang.ada:31058 Date: 2016-07-11T11:47:20-07:00 List-Id: On Monday, July 11, 2016 at 10:50:24 AM UTC-4, Simon Wright wrote: > I have 64-bit Debian Jessie (running under VMware Fusion). I don't quite understand your problem. If you feel that GCC should have re= gistered your compiler under one of hundreds of obsolete machine architectu= res, Waah! x86-64 is a superset of i686, and a boatload of other architect= ures. If you really want to generate i686 code, -march=3Di686 and usually -mtune= =3Di686 as well should do the trick. -march=3Dnative and -mtune=3Dnative w= ill generate code for the specific machine hardware you are running on. (I= haven't tested what you get when you run on a virtual machine.) I also ha= ven't checked on how to run strict x86 (286 or earlier) code on x86-64 mach= ines. Normally OSes today will run code in (per compilation unit) either l= ong (64-bit) mode or compatibility (32-bit) mode. But no compiler should b= e generating the deprecated instructions that were eliminated from the -x86= instruction set to allow 64-bit addressing in 32-bit mode. The instructio= ns were deprecated precisely because most compilers generated more efficien= t code, and no compiler should be generating them today (or for that matter= , in this century. ;-)