-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[llgo] Building error: argument of incompatible type #100
Comments
If I remove |
When I work-around this stuff a face problems with undefined constants and:
It looks like UPD: Now trying to compile commit UPD2: It does not work, too (the same problem). |
Seems to be a duplicate of: https://groups.google.com/forum/#!topic/llgo-dev/e_qUcEzTgXs |
|
I don't think llgo is alive for a while. So, I would suggest you either fix these issues and submit patches or not spend your time on this. Maybe we'd need to remove llgo sooner than later :) |
Before considering fixing it I need to understand how useful llgo could be. If it will help to essentially reduce the size of a binary (compiled from Go source codes) then it is quite likely. But right now I just need to get it work somehow just to make the measurements. If you have somewhere at least one binary-release with prebuilt |
Note that last non-trivial commit there was more than 2 years ago. |
[dsymutil] Add DW_TAG_common_block to dieNeedsChildrenToBeMeaningful
While probing stack, the stack register is moved without dwarf information, which could cause panic if unwind the backtrace. This commit only add annotation for the inline stack probe case. Dwarf information for the loop case should be done in another patch and need further discussion. Reviewed By: nagisa Differential Revision: https://reviews.llvm.org/D99579 Co-authored-by: YangKeao <[email protected]>
llgo is not in the repo anymore. |
While probing stack, the stack register is moved without dwarf information, which could cause panic if unwind the backtrace. This commit only add annotation for the inline stack probe case. Dwarf information for the loop case should be done in another patch and need further discussion. Reviewed By: nagisa Differential Revision: https://reviews.llvm.org/D99579 Co-authored-by: YangKeao <[email protected]>
llvm#100) * [flang][OpenMP] Document `do concurent` mapping status and next steps Adds a doc to document the current status of `do concurent` mapping, its limitation, and potential next steps. * handle review comments
…mnor/vmxnor/vmclr/vmset/vmmv/vmnot` (llvm#100) * [Clang][XTHeadVector] Implement 16.1 `vmand{n}/vmnand/vmxor/vmor{n}/vmnor/vmxnor` * [Clang][XTHeadVector] Test 16.1 `vmand{n}/vmnand/vmxor/vmor{n}/vmnor/vmxnor` * [Clang][XTHeadVector] Test 16.1 `vmand{n}/vmnand/vmxor/vmor{n}/vmnor/vmxnor` * [Clang][XTHeadVector] Implement wrappers 16.1 `vmand{n}/vmnand/vmxor/vmor{n}/vmnor/vmxnor`
…n't currently matter) (llvm#100) Co-authored-by: Daisy Hollman <[email protected]>
Hello.
Results into:
On Debian Buster.
The failed command is:
It would've been nice to know which code-line (of the
runtime
package) causes this error.The text was updated successfully, but these errors were encountered: