This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See crosstool-NG for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Jasmin, Bryan, All, I was just waiting for a Bryan approval about the selected - so called - standard samples. For now I have selected: * arm-unknown-eabi * armeb-unknown-eabi * arm-unknown-linux-gnueabi * armeb-unknown-linux-gnueabi I think it's a good start. We could add the other later. To go faster, I have created a pull request as it is: https://github.com/crosstool-ng/crosstool-ng/pull/180 Regards, JML 2015-09-22 0:55 GMT+02:00 Jasmin J. <jasmin@anw.at>: > Jean-Marie, > >>> If, it is OK for you, I can finish the travis part. I just need to >>> identify the "standard" samples. >> From my point you have the "OK". It is better to start with a few tests, than >> nothing (like now). >> When someone of us has time, we can add more (GCC/binutils/... version). > I haven't seen a pull request from you nor any new commit on your branch. > What else is missing to continue with this? > > BR > Jasmin > > ********************************************************************* > > On 2015-09-16 16:50, Jasmin J. wrote: >> Jean-Marie, >> >>> This way we can quickly identify regression on standard samples with >>> travis, and run full regression test when developing / reworking some >>> major features. >> I see the problem, that the samples doesn't define a gcc/binutils/... version. >> So the tests are done with the default (newest) versions of the tools. >> If we go the direction samples, then we should define the most important >> configurations for older GCC versions, too. I don't know which combination(s) >> would be representative. This is something Bryan can do best, I think. >> >> Maybe we don't need to define this combinations within the samples. We can >> define this in the travis-ci configuration, I guess. >> If you look here: >> http://docs.travis-ci.com/user/customizing-the-build/#Build-Matrix >> -> Explicity Including Builds >> Can be used to define an additional env: for the GCC/binutils/... version. >> >>> This way we can quickly identify regression on standard samples with >>> travis, and run full regression test when developing / reworking some >>> major features. >> I agree! >> >>> If, it is OK for you, I can finish the travis part. I just need to >>> identify the "standard" samples. >>>From my point you have the "OK". It is better to start with a few tests, than >> nothing (like now). >> When someone of us has time, we can add more (GCC/binutils/... version). >> >> BR >> Jasmin >> >> -- >> For unsubscribe information see http://sourceware.org/lists.html#faq >> -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |