travis CI #1
Merged
travis CI #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 12 commits
August 7, 2016 16:55
it doesn't work on macOS
Contributor
Author
|
Not quite why |
paoloteti
added a commit
to paoloteti/compiler-builtins
that referenced
this pull request
Feb 3, 2018
Here We need `extern "C"` to generate `aapcs` or `aapcs-vfp` calls
depending on target configuration.
Doing this LLVM generate:
00005614 <nesf2vfp>:
5614: eeb40ae0 vcmpe.f32 s0, s1
5618: e3a00000 mov r0, #0
561c: eef1fa10 vmrs APSR_nzcv, fpscr
5620: 13000001 movwne r0, rust-lang#1
5624: e12fff1e bx lr
That's exactly what We need
paoloteti
added a commit
to paoloteti/compiler-builtins
that referenced
this pull request
Feb 3, 2018
Here We need `extern "C"` to generate `aapcs` or `aapcs-vfp` calls
depending on target configuration.
Doing this LLVM generate:
00005614 <nesf2vfp>:
5614: eeb40ae0 vcmpe.f32 s0, s1
5618: e3a00000 mov r0, #0
561c: eef1fa10 vmrs APSR_nzcv, fpscr
5620: 13000001 movwne r0, rust-lang#1
5624: e12fff1e bx lr
That's exactly what We need
paoloteti
added a commit
to paoloteti/compiler-builtins
that referenced
this pull request
Feb 3, 2018
Here We need `extern "C"` to generate `aapcs` or `aapcs-vfp` calls
depending on target configuration.
Doing this LLVM generate:
00005614 <nesf2vfp>:
5614: eeb40ae0 vcmpe.f32 s0, s1
5618: e3a00000 mov r0, #0
561c: eef1fa10 vmrs APSR_nzcv, fpscr
5620: 13000001 movwne r0, rust-lang#1
5624: e12fff1e bx lr
That's exactly what We need
paoloteti
added a commit
to paoloteti/compiler-builtins
that referenced
this pull request
Feb 3, 2018
Here We need `extern "C"` to generate `aapcs` or `aapcs-vfp` calls
depending on target configuration.
Doing this LLVM generate:
00005614 <nesf2vfp>:
5614: eeb40ae0 vcmpe.f32 s0, s1
5618: e3a00000 mov r0, #0
561c: eef1fa10 vmrs APSR_nzcv, fpscr
5620: 13000001 movwne r0, rust-lang#1
5624: e12fff1e bx lr
That's exactly what We need
paoloteti
added a commit
to paoloteti/compiler-builtins
that referenced
this pull request
Feb 3, 2018
Here We need `extern "C"` to generate `aapcs` or `aapcs-vfp` calls
depending on target configuration.
Doing this LLVM generate:
00005614 <nesf2vfp>:
5614: eeb40ae0 vcmpe.f32 s0, s1
5618: e3a00000 mov r0, #0
561c: eef1fa10 vmrs APSR_nzcv, fpscr
5620: 13000001 movwne r0, rust-lang#1
5624: e12fff1e bx lr
That's exactly what We need
paoloteti
added a commit
to paoloteti/compiler-builtins
that referenced
this pull request
Feb 4, 2018
Here We need `extern "C"` to generate `aapcs` or `aapcs-vfp` calls
depending on target configuration.
Doing this LLVM generate:
00005614 <nesf2vfp>:
5614: eeb40ae0 vcmpe.f32 s0, s1
5618: e3a00000 mov r0, #0
561c: eef1fa10 vmrs APSR_nzcv, fpscr
5620: 13000001 movwne r0, rust-lang#1
5624: e12fff1e bx lr
That's exactly what We need.
da-x
added a commit
to da-x/compiler-builtins
that referenced
this pull request
Jul 23, 2019
In order for GDB to correctly backtrace a stack overflow, it needs CFI information in __rust_probestack. This turns the following backtrace, ``` >> bt #0 0x0000555555576f73 in __rust_probestack () at /cargo/registry/src/cf-workers-proxy-9e9.pages.dev-1ecc6299db9ec823/compiler_builtins-0.1.14/src/probestack.rs:55 Backtrace stopped: Cannot access memory at address 0x7fffff7fedf0 ``` To this: ``` >>> bt #0 0x0000555555574e47 in __rust_probestack () rust-lang#1 0x00005555555595ba in test::main () rust-lang#2 0x00005555555594f3 in std::rt::lang_start::{{closure}} () rust-lang#3 0x0000555555561ae3 in std::panicking::try::do_call () rust-lang#4 0x000055555556595a in __rust_maybe_catch_panic () rust-lang#5 0x000055555555af9b in std::rt::lang_start_internal () rust-lang#6 0x00005555555594d5 in std::rt::lang_start () rust-lang#7 0x000055555555977b in main () ```
da-x
added a commit
to da-x/compiler-builtins
that referenced
this pull request
Jul 23, 2019
In order for GDB to correctly backtrace a stack overflow, it needs CFI information in __rust_probestack. This turns the following backtrace, ``` >> bt #0 0x0000555555576f73 in __rust_probestack () at /cargo/registry/src/cf-workers-proxy-9e9.pages.dev-1ecc6299db9ec823/compiler_builtins-0.1.14/src/probestack.rs:55 Backtrace stopped: Cannot access memory at address 0x7fffff7fedf0 ``` To this: ``` >>> bt #0 0x0000555555574e47 in __rust_probestack () rust-lang#1 0x00005555555595ba in test::main () rust-lang#2 0x00005555555594f3 in std::rt::lang_start::{{closure}} () rust-lang#3 0x0000555555561ae3 in std::panicking::try::do_call () rust-lang#4 0x000055555556595a in __rust_maybe_catch_panic () rust-lang#5 0x000055555555af9b in std::rt::lang_start_internal () rust-lang#6 0x00005555555594d5 in std::rt::lang_start () rust-lang#7 0x000055555555977b in main () ```
da-x
added a commit
to da-x/compiler-builtins
that referenced
this pull request
Jul 23, 2019
In order for GDB to correctly backtrace a stack overflow, it needs CFI information in __rust_probestack. This turns the following backtrace, ``` >> bt #0 0x0000555555576f73 in __rust_probestack () at /cargo/registry/src/cf-workers-proxy-9e9.pages.dev-1ecc6299db9ec823/compiler_builtins-0.1.14/src/probestack.rs:55 Backtrace stopped: Cannot access memory at address 0x7fffff7fedf0 ``` To this: ``` >>> bt #0 0x0000555555574e47 in __rust_probestack () rust-lang#1 0x00005555555595ba in test::main () rust-lang#2 0x00005555555594f3 in std::rt::lang_start::{{closure}} () rust-lang#3 0x0000555555561ae3 in std::panicking::try::do_call () rust-lang#4 0x000055555556595a in __rust_maybe_catch_panic () rust-lang#5 0x000055555555af9b in std::rt::lang_start_internal () rust-lang#6 0x00005555555594d5 in std::rt::lang_start () rust-lang#7 0x000055555555977b in main () ```
da-x
added a commit
to da-x/compiler-builtins
that referenced
this pull request
Jul 23, 2019
In order for GDB to correctly backtrace a stack overflow, it needs CFI information in __rust_probestack. This turns the following backtrace, ``` >> bt #0 0x0000555555576f73 in __rust_probestack () at /cargo/registry/src/cf-workers-proxy-9e9.pages.dev-1ecc6299db9ec823/compiler_builtins-0.1.14/src/probestack.rs:55 Backtrace stopped: Cannot access memory at address 0x7fffff7fedf0 ``` To this: ``` >>> bt #0 0x0000555555574e47 in __rust_probestack () rust-lang#1 0x00005555555595ba in test::main () rust-lang#2 0x00005555555594f3 in std::rt::lang_start::{{closure}} () rust-lang#3 0x0000555555561ae3 in std::panicking::try::do_call () rust-lang#4 0x000055555556595a in __rust_maybe_catch_panic () rust-lang#5 0x000055555555af9b in std::rt::lang_start_internal () rust-lang#6 0x00005555555594d5 in std::rt::lang_start () rust-lang#7 0x000055555555977b in main () ```
da-x
added a commit
to da-x/compiler-builtins
that referenced
this pull request
Jul 23, 2019
In order for GDB to correctly backtrace a stack overflow, it needs CFI information in __rust_probestack. This turns the following backtrace, ``` >> bt #0 0x0000555555576f73 in __rust_probestack () at /cargo/registry/src/cf-workers-proxy-9e9.pages.dev-1ecc6299db9ec823/compiler_builtins-0.1.14/src/probestack.rs:55 Backtrace stopped: Cannot access memory at address 0x7fffff7fedf0 ``` To this: ``` >>> bt #0 0x0000555555574e47 in __rust_probestack () rust-lang#1 0x00005555555595ba in test::main () rust-lang#2 0x00005555555594f3 in std::rt::lang_start::{{closure}} () rust-lang#3 0x0000555555561ae3 in std::panicking::try::do_call () rust-lang#4 0x000055555556595a in __rust_maybe_catch_panic () rust-lang#5 0x000055555555af9b in std::rt::lang_start_internal () rust-lang#6 0x00005555555594d5 in std::rt::lang_start () rust-lang#7 0x000055555555977b in main () ```
da-x
added a commit
to da-x/compiler-builtins
that referenced
this pull request
Jul 23, 2019
In order for GDB to correctly backtrace a stack overflow, it needs CFI information in __rust_probestack. This turns the following backtrace, ``` >> bt #0 0x0000555555576f73 in __rust_probestack () at /cargo/registry/src/cf-workers-proxy-9e9.pages.dev-1ecc6299db9ec823/compiler_builtins-0.1.14/src/probestack.rs:55 Backtrace stopped: Cannot access memory at address 0x7fffff7fedf0 ``` To this: ``` >>> bt #0 0x0000555555574e47 in __rust_probestack () rust-lang#1 0x00005555555595ba in test::main () rust-lang#2 0x00005555555594f3 in std::rt::lang_start::{{closure}} () rust-lang#3 0x0000555555561ae3 in std::panicking::try::do_call () rust-lang#4 0x000055555556595a in __rust_maybe_catch_panic () rust-lang#5 0x000055555555af9b in std::rt::lang_start_internal () rust-lang#6 0x00005555555594d5 in std::rt::lang_start () rust-lang#7 0x000055555555977b in main () ```
da-x
added a commit
to da-x/compiler-builtins
that referenced
this pull request
Jul 24, 2019
This turns the following backtrace, ``` >> bt #0 0x0000555555576f73 in __rust_probestack () at /cargo/registry/src/cf-workers-proxy-9e9.pages.dev-1ecc6299db9ec823/compiler_builtins-0.1.14/src/probestack.rs:55 Backtrace stopped: Cannot access memory at address 0x7fffff7fedf0 ``` To this: ``` >>> bt #0 0x0000555555574e47 in __rust_probestack () rust-lang#1 0x00005555555595ba in test::main () rust-lang#2 0x00005555555594f3 in std::rt::lang_start::{{closure}} () rust-lang#3 0x0000555555561ae3 in std::panicking::try::do_call () rust-lang#4 0x000055555556595a in __rust_maybe_catch_panic () rust-lang#5 0x000055555555af9b in std::rt::lang_start_internal () rust-lang#6 0x00005555555594d5 in std::rt::lang_start () rust-lang#7 0x000055555555977b in main () ```
da-x
added a commit
to da-x/compiler-builtins
that referenced
this pull request
Jul 24, 2019
This turns the following backtrace, ``` >> bt #0 0x0000555555576f73 in __rust_probestack () at /cargo/registry/src/cf-workers-proxy-9e9.pages.dev-1ecc6299db9ec823/compiler_builtins-0.1.14/src/probestack.rs:55 Backtrace stopped: Cannot access memory at address 0x7fffff7fedf0 ``` To this: ``` >>> bt #0 0x0000555555574e47 in __rust_probestack () rust-lang#1 0x00005555555595ba in test::main () rust-lang#2 0x00005555555594f3 in std::rt::lang_start::{{closure}} () rust-lang#3 0x0000555555561ae3 in std::panicking::try::do_call () rust-lang#4 0x000055555556595a in __rust_maybe_catch_panic () rust-lang#5 0x000055555555af9b in std::rt::lang_start_internal () rust-lang#6 0x00005555555594d5 in std::rt::lang_start () rust-lang#7 0x000055555555977b in main () ```
tgross35
pushed a commit
to tgross35/compiler-builtins
that referenced
this pull request
Feb 23, 2025
tgross35
pushed a commit
to tgross35/compiler-builtins
that referenced
this pull request
Feb 23, 2025
pull from master
This comment has been minimized.
This comment has been minimized.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.