subject:"\[Bug other\/79046\] g\+\+ \-print\-file\-name=plugin uses full version number in path"

[Bug other/79046] g++ -print-file-name=plugin uses full version number in path

2018-02-21 Thread jakub at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79046 Jakub Jelinek changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug other/79046] g++ -print-file-name=plugin uses full version number in path

2018-02-21 Thread egallager at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79046 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org --- Comment

[Bug other/79046] g++ -print-file-name=plugin uses full version number in path

2017-01-25 Thread jakub at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79046 --- Comment #12 from Jakub Jelinek --- Author: jakub Date: Wed Jan 25 11:54:36 2017 New Revision: 244895 URL: https://gcc.gnu.org/viewcvs?rev=244895&root=gcc&view=rev Log: PR other/79046 * configure.ac: Add GCC_BASE_VER.

[Bug other/79046] g++ -print-file-name=plugin uses full version number in path

2017-01-21 Thread jakub at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79046 --- Comment #11 from Jakub Jelinek --- Author: jakub Date: Sat Jan 21 08:47:11 2017 New Revision: 244742 URL: https://gcc.gnu.org/viewcvs?rev=244742&root=gcc&view=rev Log: PR other/79046 libatomic/ * testsuite/Makefile.am (gcc_ve

[Bug other/79046] g++ -print-file-name=plugin uses full version number in path

2017-01-20 Thread jakub at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79046 --- Comment #10 from Jakub Jelinek --- Author: jakub Date: Fri Jan 20 08:27:29 2017 New Revision: 244684 URL: https://gcc.gnu.org/viewcvs?rev=244684&root=gcc&view=rev Log: PR other/79046 liboffloadmic/ * aclocal.m4: Regenerated.

[Bug other/79046] g++ -print-file-name=plugin uses full version number in path

2017-01-19 Thread jakub at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79046 --- Comment #9 from Jakub Jelinek --- Author: jakub Date: Thu Jan 19 12:23:00 2017 New Revision: 244627 URL: https://gcc.gnu.org/viewcvs?rev=244627&root=gcc&view=rev Log: PR other/79046 * aclocal.m4: Include ../config/acx.m4.

[Bug other/79046] g++ -print-file-name=plugin uses full version number in path

2017-01-17 Thread jakub at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79046 --- Comment #8 from Jakub Jelinek --- Author: jakub Date: Tue Jan 17 09:38:48 2017 New Revision: 244521 URL: https://gcc.gnu.org/viewcvs?rev=244521&root=gcc&view=rev Log: PR other/79046 * configure: Regenerated. config/ *

[Bug other/79046] g++ -print-file-name=plugin uses full version number in path

2017-01-12 Thread pinskia at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79046 --- Comment #7 from Andrew Pinski --- (In reply to Dave Johansen from comment #6) > Could that be made a guarantee? Right now, having to build plugins against > the full version of GCC is a major pain for distributions and saying that > GCC plugi

[Bug other/79046] g++ -print-file-name=plugin uses full version number in path

2017-01-12 Thread davejohansen at gmail dot com

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79046 --- Comment #6 from Dave Johansen --- Could that be made a guarantee? Right now, having to build plugins against the full version of GCC is a major pain for distributions and saying that GCC plugins are API/ABI stable for a major version would el

[Bug other/79046] g++ -print-file-name=plugin uses full version number in path

2017-01-11 Thread jakub at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79046 --- Comment #5 from Jakub Jelinek --- There is no such guarantee, it can change any time, even in changes not reflected in X.Y.Z version. That said, after X.1 is released, they change not very frequently.

[Bug other/79046] g++ -print-file-name=plugin uses full version number in path

2017-01-11 Thread boris at kolpackov dot net

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79046 --- Comment #4 from Boris Kolpackov --- Another question is whether GCC guarantees that its APIs (as can be used by a plugin; e.g., AST) are binary compatible across Y.Z in GCC X.Y.Z?

[Bug other/79046] g++ -print-file-name=plugin uses full version number in path

2017-01-10 Thread davejohansen at gmail dot com

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79046 --- Comment #3 from Dave Johansen --- What are the chances that either of those changes will make it into the 7 release?