> If gcc is branched now, does this mean that the libgcc ABI is now set > in stone? It was our intention to have an ABI that would live for a long time or at least be backward-compatible. So anything that conflicts with that needs to be resolved in a hurry.