Skip to content
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.

Sign up for GitHub

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

Jump to bottom

x/build: add builder that tests usage of gccgo to bootstrap go gc #40875

Open
martisch opened this issue Aug 18, 2020 · 2 comments
Open

x/build: add builder that tests usage of gccgo to bootstrap go gc #40875

martisch opened this issue Aug 18, 2020 · 2 comments
Labels
Builders x/build issues (builders, bots, dashboards) NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. new-builder
Milestone
Unreleased

Comments

@martisch
Copy link
Contributor

There have been issues now and in the past about bootstrapping Go gc from gccgo being broken #40855, #30771.

Documentation at https://golang.org/doc/install/source#bootstrapFromGccgo suggests that bootstraping from gccgo is supported.

If this is the case I suggest we add a builder for that. To not be blocked on ressources I would assume a build only linux/amd64 builder would suffice to catch bootstrap issues.

/cc @ianlancetaylor @dmitshur
@gopherbot gopherbot added the Builders x/build issues (builders, bots, dashboards) label Aug 18, 2020
@gopherbot gopherbot modified the milestones: Unreleased, Gccgo Aug 18, 2020
@martisch martisch added NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made. new-builder labels Aug 18, 2020
@martisch martisch changed the title x/build: add builder that uses gccgo to bootstrap go gc x/build: add builder that tests usage of gccgo to bootstrap go gc Aug 18, 2020
@martisch martisch modified the milestones: Gccgo, Unreleased Aug 18, 2020
@dmitshur
Copy link
Contributor

Given we say it is supported, I agree we should aim to have a test or a builder to confirm that it hasn't regressed.

We have some make.bash-only builders (e.g., search for CompileOnly in x/build/dashboard), so this can probably be arranged in a similar way.

Which version of Gccgo should be tested, and how often should we aim to update it?

/cc @cagedmantis @toothrot @andybons

@dmitshur dmitshur added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. and removed NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made. labels Aug 20, 2020
@ianlancetaylor
Copy link
Contributor

gccgo is released as part of GCC, and a new major version of GCC is released once a year.

@apaprocki apaprocki mentioned this issue May 18, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Builders x/build issues (builders, bots, dashboards) NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. new-builder
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
4 participants
@martisch @dmitshur @ianlancetaylor @gopherbot