https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106899
Mark Wielaard changed:
What|Removed |Added
CC||mark at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106899
--- Comment #5 from Richard Biener ---
The resource issue is probably a non-issue these days
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106899
--- Comment #4 from Andrew Pinski ---
So the issue is when we do a release, do a full build of GCC.
Doing a snapshot does NOT do the full build because of resource constraints.
We have at least any one time, 4 snapshots happening during the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106899
--- Comment #3 from Sam James ---
Yeah, I understand it's not an error per se, just wondering if it could be
considered to add them.
It looks like they're generated from the same script used for releases:
maintainer-scripts/gcc_release (as it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106899
--- Comment #2 from Andrew Pinski ---
"Public releases and weekly snapshots of the development sources are also
available via HTTPS."
"Necessary to build GCC documentation during development because the generated
output files are not included
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106899
--- Comment #1 from Andrew Pinski ---
Right this is done on purpose as snapshots are just snapshots of the sources
directly from the git.
