On Mon, 25 Jan 2021, Patrick McGehearty wrote: > On 1/21/2021 5:04 PM, Joseph Myers wrote: > > On Fri, 18 Dec 2020, Patrick McGehearty via Gcc-patches wrote: > > > > > TEST Data > > I'd still like to see the test data / code used to produce the accuracy > > and performance results made available somewhere (presumably with a link > > then being provided in the commit message). > > I've packaged up the code/scripts/README and some data in a directory. > I had it ready last time and meant to provide it, but it slipped my mind > while I was preparing the patch. Total size is under a megabyte, so moving > it around should not be a problem. > > Is this sort of development support code usually kept somewhere in the gcc > tree or > should it be placed elsewhere, like in my personal github directory?
I think that sort of thing (when it's too big to just attach to the email with the patch - if it can be attached to the email, or to a relevant open bug in Bugzilla, that's the simplest thing to do) would typically go somewhere else rather than in the GCC tree. -- Joseph S. Myers jos...@codesourcery.com
