Project Ortega BCM5719 LLVM https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1 2019-01-19T08:50:56+00:00 2019-01-19T08:50:56+00:00 Chandler Carruth chandlerc@gmail.com 2019-01-19T08:50:56+00:00 urn:sha1:2946cd701067404b99c39fb29dc9c74bd7193eb3 to reflect the new license. We understand that people may be surprised that we're moving the header entirely to discuss the new license. We checked this carefully with the Foundation's lawyer and we believe this is the correct approach. Essentially, all code in the project is now made available by the LLVM project under our new license, so you will see that the license headers include that license only. Some of our contributors have contributed code under our old license, and accordingly, we have retained a copy of our old license notice in the top-level files in each project and repository. llvm-svn: 351636 2018-08-23T03:40:31+00:00 JF Bastien jfbastien@apple.com 2018-08-23T03:40:31+00:00 urn:sha1:a1cca516eb745b115a0228592651741ca3c810ff When complaining that the triple is incompatible with all targets, print out the triple not just a generic error about triples not matching. llvm-svn: 340509 2018-07-30T19:41:25+00:00 Fangrui Song maskray@google.com 2018-07-30T19:41:25+00:00 urn:sha1:f78650a8deca216b858827ff430972c114a60a7a sed -Ei 's/[[:space:]]+$//' include/**/*.{def,h,td} lib/**/*.{cpp,h} llvm-svn: 338293 2017-11-15T23:55:44+00:00 Daniel Sanders daniel_l_sanders@apple.com 2017-11-15T23:55:44+00:00 urn:sha1:725584e26d79d00ad4b14cab15babc4b4499d22e Summary: Make it possible to feed runtime information back to tablegen to enable profile-guided tablegen-eration, detection of untested tablegen definitions, etc. Being a cross-compiler by nature, LLVM will potentially collect data for multiple architectures (e.g. when running 'ninja check'). We therefore need a way for TableGen to figure out what data applies to the backend it is generating at the time. This patch achieves that by including the name of the 'def X : Target ...' for the backend in the TargetRegistry. Reviewers: qcolombet Reviewed By: qcolombet Subscribers: jholewinski, arsenm, jyknight, aditya_nandakumar, sdardis, nemanjai, ab, nhaehnle, t.p.northover, javed.absar, qcolombet, llvm-commits, fedor.sergeev Differential Revision: https://reviews.llvm.org/D39742 llvm-svn: 318352 2017-06-06T21:54:04+00:00 Dimitry Andric dimitry@andric.com 2017-06-06T21:54:04+00:00 urn:sha1:bc3feaaa884021ee3d76b70a3a2a2617eb261148 Summary: I would like to add printing of registered targets to clang's version information. For this to work correctly, the VersionPrinter logic in CommandLine.cpp should support printing to arbitrary raw_ostreams, instead of always defaulting to outs(). Add a raw_ostream& parameter to the function pointer type used for VersionPrinter, and while doing so, introduce a typedef for convenience. Note that VersionPrinter::print() will still default to using outs(), the clang part will necessarily go into a separate review. Reviewers: beanz, chandlerc, dberris, mehdi_amini, zturner Reviewed By: mehdi_amini Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D33899 llvm-svn: 304835 2016-10-01T07:08:23+00:00 Mehdi Amini mehdi.amini@apple.com 2016-10-01T07:08:23+00:00 urn:sha1:9af9a9d5f93b617a8d3c7ce75812acf6386d6051 This reverts commit r283017. Creates an infinite loop somehow. llvm-svn: 283019 2016-10-01T06:25:30+00:00 Mehdi Amini mehdi.amini@apple.com 2016-10-01T06:25:30+00:00 urn:sha1:cd354a659b89cf5fed6a578ec3fb665607c573ac llvm-svn: 283017 2016-08-12T00:18:03+00:00 David Majnemer david.majnemer@gmail.com 2016-08-12T00:18:03+00:00 urn:sha1:562e82945eec22679ae20fdb19b84dcd6959bf90 No functionality change is intended. llvm-svn: 278443 2016-01-28T22:55:45+00:00 Rafael Espindola rafael.espindola@gmail.com 2016-01-28T22:55:45+00:00 urn:sha1:26e65817faf6cf4dae494bfa466523fe3efa3fa8 The program using this code may not have it. Patch by Wilfred Hughes. llvm-svn: 259106 2015-05-11T22:20:48+00:00 David Blaikie dblaikie@gmail.com 2015-05-11T22:20:48+00:00 urn:sha1:46c561c19e5b9d8bb77f7b98f0803b4c386243e4 The TargetRegistry is just a namespace-like class, instantiated in one place to use a range-based for loop. Instead, expose access to the registry via a range-based 'targets()' function instead. This makes most uses a bit awkward/more verbose - but eventually we should just add a range-based find_if function which will streamline these functions. I'm happy to mkae them a bit awkward in the interim as encouragement to improve the algorithms in time. llvm-svn: 237059