wmobit

Possibly -ffreestanding will help

The _fltused handling is quite crude: https://github.com/llvm/llvm-project/blob/5cfd02f44a43a2e2a0...

TLDR it's going to emit the reference if it's targeting MSVC and there's any float typed reference. You'd need to do something to avoid it, other than avoiding float types.

Presumably you are compiling for the MSVC ABI. Trying to plug your own runtime that doesn't behave exactly as the MSVC scheme isn't going to just work out of the box. The compiler has to know the details of the ABI you are targeting, if you're doing your own thing the compiler would need to treat that as a separate ABI. I'm not sure there's a triple now that means MSVC-like-freestanding.

The same logic applies on the clang driver side. The ABI expects to link those libraries, so it will.

I'd go so far as to say it's the exact opposite. It's faster and easier to change the hardware than the software.

clang does have pragma clang fp to enable a subset of fast math flags within a scope

This couldn't have a worse name. It's already used inside clang, and llvm. Searching "llvm CodeGen" will never find this.

Chrome is available on the App Store

It's really not. It's barely an abstraction over LLVM IR

I live on El Camino and frequently take the bus. It's a 40 minute walk to the nearest caltrain station

The keurig actually does have tea pods, which produce pretty awful tea

clBLAS

There is an OpenCL profiler for AMD, and library equivalents for those in clBLAS / clFFT

There isn't really anything fundamentally that would make CUDA faster that OpenCL. There aren't any huge semantic differences between them.

No, unfortunately front ends still need to be aware of some of the ABI details of the target to produce the IR for it.

I used to use it before working on it was my job.

But the 64-bit pointer support isn't there yet, so it's not super useful. You can't use it all within the same program

Most (probably nearly all, I've never seen one that doesn't) have bathrooms with showers.

Dear everyone, please stop using C as a compile target. Thanks.

I also think it mostly means the president won't see anybody's penis.

As if MS will implement C1X. They haven't caught up to the last C standard from 12 years ago

The alloca usage here terrifies me.

No, it's totally a sine wave.

Comments on saved ones might be nice. For example, on the one I started on, there appears to be a tiger in Colorado. I have an urge to comment and ask if that is in fact a tiger.

You don't use experiments to 'derive' the speed of light. You use Maxwell's equations.

Note the 'Automatic' qualifier on reference counting

Such is impossible under current copyright law

Saying the GPL is draconian and limits freedom is like saying the 13th amendment limits freedom since it takes away your right to own slaves.

Perhaps the people using JavaScript are the more likely the kinds of people to go asking more questions.

I have a feeling he hasn't really been hired by Apple yet.

I saw nothing about mathematics here; this was all about arithmetic.

Google has said before they didn't use Clang and LLVM because of performance issues. GCC is far from dead, and probably never will. Clang generated code is still typically 10-20% slower than GCC. Lots of companies work on GCC, including Google, Intel, AMD, IBM, Red Hat and others.