-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Closed
Labels
bugzillaIssues migrated from bugzillaIssues migrated from bugzillallvm-toolsAll llvm tools that do not have corresponding tagAll llvm tools that do not have corresponding tagobsoleteIssues with old (unsupported) versions of LLVMIssues with old (unsupported) versions of LLVMwontfixIssue is real, but we can't or won't fix it. Not invalidIssue is real, but we can't or won't fix it. Not invalid
Description
| Bugzilla Link | 2007 |
| Version | trunk |
| OS | Linux |
| Reporter | LLVM Bugzilla Contributor |
| CC | @lattner |
Extended Description
The reason for this is that the compiler itself is built
using setjump/longjump style exceptions which is not
supported by LLVM (normal code built by the compiler uses
dwarf zero-cost style exceptions which are supported by LLVM).
Exceptions are raised inside the compiler when it builds
the runtime (due to processing files containing pragmas
for VAX) and need to be caught. The exceptions are caught
if the new compiler was built by the system compiler, but
not if it was built using the llvm-gcc Ada compiler, which
is what happens during bootstrap.
This could be fixed by adding sj/lj exception support to
LLVM, or by modifying the build system so that the compiler
uses dwarf zcx internally.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugzillaIssues migrated from bugzillaIssues migrated from bugzillallvm-toolsAll llvm tools that do not have corresponding tagAll llvm tools that do not have corresponding tagobsoleteIssues with old (unsupported) versions of LLVMIssues with old (unsupported) versions of LLVMwontfixIssue is real, but we can't or won't fix it. Not invalidIssue is real, but we can't or won't fix it. Not invalid