Re: GNU/GCC optimizing

From	Francois LE COAT <lecoat@atari.org>
Newsgroups	comp.sys.atari.st
Subject	Re: GNU/GCC optimizing
Date	2015-10-08 21:31 +0200
Organization	Aioe.org NNTP Server
Message-ID	<mv6g9i$sb0$1@speranza.aioe.org> (permalink)
References	(5 earlier) <slrnn10l69.438.news-1326478115@a-tuin.ms.intern> <mur8pi$cne$1@speranza.aioe.org> <mus1n2$poh$1@news.albasani.net> <mus63k$mi1$1@speranza.aioe.org> <4d5f5390-6f86-4118-ab94-b30efb4acadf@googlegroups.com>

Show all headers | View raw

Hi MiKRO,

Miro Kropáček writes:
>> I'm afraid if I make that changes, my Eureka 2.12 sources will only
>> be compatible with GNU/GCC 4, and not any other C compiler.
>
> This is not true. On the contrary, most likely you'll discover hidden bugs in your code. And of course the source will stay compatible, as mentioned, the compiler is now more strict but that doesn't mean it doesn't adhere to the C standard.
>
> So it boils down to the fact whether you're willing to change your code or you're stuck with 3.x forever. Obsolete sources require obsolete compilers.

Well, I remind you that I'm not supposed to be able to use GNU/GCC 4
to build my Eureka 2.12 program. The great advantage with GNU/GCC 3
is that it understands my sources, producing warnings that it
can tolerates. The other advantage is that it includes 16bits
libraries, that are mandatory to build my software, for compatibility
with PURE C and furthermore binary compatibility with the ATARI ST.

Should I abandon the opportunity to build an ATARI ST software to
sacrify to the modernity of GNU/GCC 4, because it's new. What
improvements does it bring to the m68k-atari-mint target ? I'm
suspecting there's more drawbacks than improvements with GNU/GCC 4.

Why doesn't it include 16bits libs, breaking backward compatibility ?

Thanks for your answer.

Best regards,

-- 
François LE COAT
Author of Eureka 2.12 (2D Graph Describer, 3D Modeller)
http://eureka.atari.org/

Back to comp.sys.atari.st | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

GNU/GCC optimizing Francois LE COAT <lecoat@atari.org> - 2015-09-30 23:45 +0200
  Re: GNU/GCC optimizing Miro Kropáček <miro.kropacek@gmail.com> - 2015-09-30 23:18 -0700
    Re: GNU/GCC optimizing Francois LE COAT <lecoat@atari.org> - 2015-10-01 21:41 +0200
      Re: GNU/GCC optimizing Miro Kropáček <miro.kropacek@gmail.com> - 2015-10-01 23:12 -0700
        Re: GNU/GCC optimizing Francois LE COAT <lecoat@atari.org> - 2015-10-03 16:07 +0200
          Re: GNU/GCC optimizing Michael Schwingen <news-1326478115@discworld.dascon.de> - 2015-10-03 22:20 +0000
            Re: GNU/GCC optimizing Francois LE COAT <lecoat@atari.org> - 2015-10-04 15:15 +0200
              Re: GNU/GCC optimizing Michael Schwingen <news-1326478115@discworld.dascon.de> - 2015-10-04 18:19 +0000
                Re: GNU/GCC optimizing Francois LE COAT <lecoat@atari.org> - 2015-10-04 22:30 +0200
                Re: GNU/GCC optimizing Michael Schwingen <news-1326478115@discworld.dascon.de> - 2015-10-06 16:38 +0000
                Re: GNU/GCC optimizing Francois LE COAT <lecoat@atari.org> - 2015-10-06 21:51 +0200
                Re: GNU/GCC optimizing Michael Schwingen <news-1326478115@discworld.dascon.de> - 2015-10-07 06:55 +0000
              Re: GNU/GCC optimizing David Wade <dave.g4ugm@gmail.com> - 2015-10-04 21:20 +0100
                Re: GNU/GCC optimizing Francois LE COAT <lecoat@atari.org> - 2015-10-04 23:35 +0200
                Re: GNU/GCC optimizing Miro Kropáček <miro.kropacek@gmail.com> - 2015-10-05 02:36 -0700
                Re: GNU/GCC optimizing Francois LE COAT <lecoat@atari.org> - 2015-10-08 21:31 +0200
                Re: GNU/GCC optimizing Miro Kropáček <miro.kropacek@gmail.com> - 2015-10-08 23:55 -0700
                Re: GNU/GCC optimizing Francois LE COAT <lecoat@atari.org> - 2015-10-09 17:25 +0200
                Re: GNU/GCC optimizing Michael Schwingen <news-1326478115@discworld.dascon.de> - 2015-10-10 09:40 +0000
                Re: GNU/GCC optimizing Francois LE COAT <lecoat@atari.org> - 2015-10-10 13:07 +0200

csiph-web