On 05/24/2017 07:31 AM, Martin Schreiber wrote:
> On Wednesday 24 May 2017 15:15:15 Martin Schreiber wrote:
>> On Wednesday 24 May 2017 07:47:09 Martin Schreiber wrote:
So what's MSElang's frame rate and on what kind of machine/OS?
>>> Not ready yet.
>> Linux 32 bit
>> Intel(R) Core(TM)
On Wednesday 24 May 2017 15:15:15 Martin Schreiber wrote:
> On Wednesday 24 May 2017 07:47:09 Martin Schreiber wrote:
> > > So what's MSElang's frame rate and on what kind of machine/OS?
> >
> > Not ready yet.
>
> Linux 32 bit
> Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
>
> With round() operations
>
On Wednesday 24 May 2017 07:47:09 Martin Schreiber wrote:
>
> > So what's MSElang's frame rate and on what kind of machine/OS?
>
> Not ready yet.
>
Linux 32 bit
Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
With round() operations
On 2017-05-24 15:35, Jon Foster wrote:
> Interesting! Only a 25% increase between your 3.2GHz and my 1.9GHz CPUs.
No real surprise. For many many years now, GHz is not a reliable
measuring stick to measure performance differences between CPUs. A 2Ghz
Intel i7 could easily outperform a 2.5Ghz
On 2017-05-24 14:15, Martin Schreiber wrote:
> FPC 3.0.2
> -O- -> 8 FPS
> -O4 -CfSSE3 -CpCOREI -> access violation
> -O3 -CfSSE3 -CpCOREI -> access violation
> -O4 -CpCOREI -> 8.2 FPS
Bottom line FPC sucks for game development - unless you offload
pretty much everything onto a GPU -
On Wednesday 24 May 2017 15:32:05 Graeme Geldenhuys wrote:
> On 2017-05-24 14:15, Martin Schreiber wrote:
> > FPC 3.0.2
> > -O- -> 8 FPS
> > -O4 -CfSSE3 -CpCOREI -> access violation
> > -O3 -CfSSE3 -CpCOREI -> access violation
> > -O4 -CpCOREI -> 8.2 FPS
>
> Bottom line FPC sucks for game
On 05/24/2017 06:15 AM, Martin Schreiber wrote:
> On Wednesday 24 May 2017 07:47:09 Martin Schreiber wrote:
>
>>> So what's MSElang's frame rate and on what kind of machine/OS?
>> Not ready yet.
>>
> Linux 32 bit
> Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
>
> With round() operations
>
On 2017-05-24 06:47, Martin Schreiber wrote:
> That is wrong, the code is not identical. Please read the mail again,
> especially about the differences of round().
There was so many iterations of that program, I lost track of which one
I published. But I know for a fact I tried frac(), trunk()
On 2017-05-24 17:52, Martin Schreiber wrote:
> which will be optimized ("opt") and compiled to machine code ("llc") or runned
> by a just in time compiler or interpreter ("lli").
So LLVM does something like what Java's compiler does. I know nothing
about LLVM. :)
Regards,
Graeme
On 05/24/2017 06:32 AM, Graeme Geldenhuys wrote:
> On 2017-05-24 14:15, Martin Schreiber wrote:
> Bottom line FPC sucks for game development - unless you offload
> pretty much everything onto a GPU - something I was hoping wouldn't be
> needed for that project.
>
> FPC's saving grace is that
On Wednesday 24 May 2017 18:58:40 Graeme Geldenhuys wrote:
> On 2017-05-24 17:52, Martin Schreiber wrote:
> > which will be optimized ("opt") and compiled to machine code ("llc") or
> > runned by a just in time compiler or interpreter ("lli").
>
> So LLVM does something like what Java's compiler
On 05/24/2017 10:51 AM, Martin Schreiber wrote:
> On Wednesday 24 May 2017 18:58:40 Graeme Geldenhuys wrote:
>> On 2017-05-24 17:52, Martin Schreiber wrote:
>>> which will be optimized ("opt") and compiled to machine code ("llc") or
>>> runned by a just in time compiler or interpreter ("lli").
>>
On Thursday 25 May 2017 00:50:46 Jon Foster wrote:
>
>
> Apple traded out GCC for CLang / LLVM some time ago. The only downside
> I've heard about LLVM is that its slow. Like GCC & friends weren't. But I
> think a lot GCC slowness is inherited from binutils and that's probably the
> same for
On 05/24/2017 01:27 PM, Fred van
Stappen wrote:
> So LLVM does something
like what Java's compiler does.
The kernel of FreeBSD is
made by LLVM-clang compiler.
(Even if the
> So LLVM does something like what Java's compiler does.
The kernel of FreeBSD is made by LLVM-clang compiler.
(Even if the script to build the kernel needs 8 different compilers ! (that are
in fact copy the same clang compiler with 8 different names !).
Fre;D
On Wednesday 24 May 2017 17:25:02 Jon Foster wrote:
>
> MSElang is using LLVM, right? Are you using an upstream provided x86 back
> end or did you have to write that?
MSElang produces LLVM bitcode
http://llvm.org/docs/BitCodeFormat.html
which will be optimized ("opt") and compiled to machine code
16 matches
Mail list logo