Skip to content

make the gcc crate optional #143

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

Merged
merged 1 commit into from
Feb 21, 2017
Merged

make the gcc crate optional #143

merged 1 commit into from
Feb 21, 2017

Conversation

japaric
Copy link
Member

@japaric japaric commented Feb 19, 2017

it's only required when the "c" feature is enabled

r? @alexcrichton

it's only required when the "c" feature is enabled
@alexcrichton
Copy link
Member

@bors: r+

@bors
Copy link
Contributor

bors commented Feb 21, 2017

📌 Commit a2e6591 has been approved by alexcrichton

@bors
Copy link
Contributor

bors commented Feb 21, 2017

⌛ Testing commit a2e6591 with merge 0507842...

bors added a commit that referenced this pull request Feb 21, 2017
make the gcc crate optional

it's only required when the "c" feature is enabled

r? @alexcrichton
@bors
Copy link
Contributor

bors commented Feb 21, 2017

☀️ Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 0507842 to master...

@bors bors merged commit a2e6591 into master Feb 21, 2017
@japaric japaric deleted the no-gcc branch March 6, 2017 20:20
tgross35 pushed a commit to tgross35/compiler-builtins that referenced this pull request Feb 23, 2025
Fix the atan family of functions behavior with bounds checks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants