Skip to main content
replaced http://unix.stackexchange.com/ with https://unix.stackexchange.com/
Source Link

One thing worth considering is that FreeBSD is currently using GCC 4.2.1 as noted in ire_and_curses answernoted in ire_and_curses answer thus the performance comparisons aren't of 4.5 or even 4.6 aren't truly relevant to the project. Therefore, the questions you should be asking are:

  1. What are the performance gains of the new Clang vs the older GCC that the project uses?

  2. How do the same binaries compiled in GCC 4.2.1 compare to the new Clang?

Because of GCC's move to the GPL v3, FreeBSD was forced to remain using GCC 4.2.1 (GPL v2), which was released way back in 2007, and is now significantly outdated.

If Clang lags behind the current GCC but is still light years ahead of the implemented GCC in the project then their decision to evolve is well warranted and truly inspired.

One thing worth considering is that FreeBSD is currently using GCC 4.2.1 as noted in ire_and_curses answer thus the performance comparisons aren't of 4.5 or even 4.6 aren't truly relevant to the project. Therefore, the questions you should be asking are:

  1. What are the performance gains of the new Clang vs the older GCC that the project uses?

  2. How do the same binaries compiled in GCC 4.2.1 compare to the new Clang?

Because of GCC's move to the GPL v3, FreeBSD was forced to remain using GCC 4.2.1 (GPL v2), which was released way back in 2007, and is now significantly outdated.

If Clang lags behind the current GCC but is still light years ahead of the implemented GCC in the project then their decision to evolve is well warranted and truly inspired.

One thing worth considering is that FreeBSD is currently using GCC 4.2.1 as noted in ire_and_curses answer thus the performance comparisons aren't of 4.5 or even 4.6 aren't truly relevant to the project. Therefore, the questions you should be asking are:

  1. What are the performance gains of the new Clang vs the older GCC that the project uses?

  2. How do the same binaries compiled in GCC 4.2.1 compare to the new Clang?

Because of GCC's move to the GPL v3, FreeBSD was forced to remain using GCC 4.2.1 (GPL v2), which was released way back in 2007, and is now significantly outdated.

If Clang lags behind the current GCC but is still light years ahead of the implemented GCC in the project then their decision to evolve is well warranted and truly inspired.

One thing worth considering is that FreeBSD is currently using GCC 4.2.1 as noted abovenoted in ire_and_curses answer thus the performance comparisons aren't of 4.5 or even 4.6 aren't truly relevant to the project. Therefore, the questions you should be asking are:

  1. What are the performance gains of the new Clang vs the older GCC that the project uses?

  2. How do the same binaries compiled in GCC 4.2.1 compare to the new Clang?

Because of GCC's move to the GPL v3, FreeBSD was forced to remain using GCC 4.2.1 (GPL v2), which was released way back in 2007, and is now significantly outdated.

If Clang lags behind the current GCC but is still light years ahead of the implemented GCC in the project then their decision to evolve is well warranted and truly inspired.

One thing worth considering is that FreeBSD is currently using GCC 4.2.1 as noted above thus the performance comparisons aren't of 4.5 or even 4.6 aren't truly relevant to the project. Therefore, the questions you should be asking are:

  1. What are the performance gains of the new Clang vs the older GCC that the project uses?

  2. How do the same binaries compiled in GCC 4.2.1 compare to the new Clang?

Because of GCC's move to the GPL v3, FreeBSD was forced to remain using GCC 4.2.1 (GPL v2), which was released way back in 2007, and is now significantly outdated.

If Clang lags behind the current GCC but is still light years ahead of the implemented GCC in the project then their decision to evolve is well warranted and truly inspired.

One thing worth considering is that FreeBSD is currently using GCC 4.2.1 as noted in ire_and_curses answer thus the performance comparisons aren't of 4.5 or even 4.6 aren't truly relevant to the project. Therefore, the questions you should be asking are:

  1. What are the performance gains of the new Clang vs the older GCC that the project uses?

  2. How do the same binaries compiled in GCC 4.2.1 compare to the new Clang?

Because of GCC's move to the GPL v3, FreeBSD was forced to remain using GCC 4.2.1 (GPL v2), which was released way back in 2007, and is now significantly outdated.

If Clang lags behind the current GCC but is still light years ahead of the implemented GCC in the project then their decision to evolve is well warranted and truly inspired.

Removed signature, as it does not provide information relevant to the question itself.
Source Link

One thing worth considering is that FreeBSD is currently using GCC 4.2.1 as noted above thus the performance comparisons aren't of 4.5 or even 4.6 aren't truly relevant to the project. Therefore, the questions you should be asking are:

  1. What are the performance gains of the new Clang vs the older GCC that the project uses?

  2. How do the same binaries compiled in GCC 4.2.1 compare to the new Clang?

Because of GCC's move to the GPL v3, FreeBSD was forced to remain using GCC 4.2.1 (GPL v2), which was released way back in 2007, and is now significantly outdated.

If Clang lags behind the current GCC but is still light years ahead of the implemented GCC in the project then their decision to evolve is well warranted and truly inspired.

Regards,

Mikel King

Senior Editor, BSD News

http://bsdnews.net

One thing worth considering is that FreeBSD is currently using GCC 4.2.1 as noted above thus the performance comparisons aren't of 4.5 or even 4.6 aren't truly relevant to the project. Therefore, the questions you should be asking are:

  1. What are the performance gains of the new Clang vs the older GCC that the project uses?

  2. How do the same binaries compiled in GCC 4.2.1 compare to the new Clang?

Because of GCC's move to the GPL v3, FreeBSD was forced to remain using GCC 4.2.1 (GPL v2), which was released way back in 2007, and is now significantly outdated.

If Clang lags behind the current GCC but is still light years ahead of the implemented GCC in the project then their decision to evolve is well warranted and truly inspired.

Regards,

Mikel King

Senior Editor, BSD News

http://bsdnews.net

One thing worth considering is that FreeBSD is currently using GCC 4.2.1 as noted above thus the performance comparisons aren't of 4.5 or even 4.6 aren't truly relevant to the project. Therefore, the questions you should be asking are:

  1. What are the performance gains of the new Clang vs the older GCC that the project uses?

  2. How do the same binaries compiled in GCC 4.2.1 compare to the new Clang?

Because of GCC's move to the GPL v3, FreeBSD was forced to remain using GCC 4.2.1 (GPL v2), which was released way back in 2007, and is now significantly outdated.

If Clang lags behind the current GCC but is still light years ahead of the implemented GCC in the project then their decision to evolve is well warranted and truly inspired.

Source Link
Mikel King
  • 391
  • 2
  • 2
Loading