| # 03:07:27 | ccole | joins #crosstool-ng |
| # 04:26:19 | alan_o | quits : Quit: Leaving |
| # 09:56:54 | y_morin | joins #crosstool-ng |
| # 13:46:46 | ccole | quits : *.net *.split |
| # 13:47:45 | ccole | joins #crosstool-ng |
| # 15:16:04 | esbenh | quits : *.net *.split |
| # 15:16:21 | esbenh | joins #crosstool-ng |
| # 15:36:11 | smartin | joins #crosstool-ng |
| # 15:59:20 | smartin_ | joins #crosstool-ng |
| # 16:01:16 | smartin | quits : Ping timeout: 245 seconds |
| # 16:22:20 | smartin_ | is now known as: smartin |
| # 18:50:50 | alan_o | joins #crosstool-ng |
| # 18:54:50 | alan_o | So I feel dumb for asking this, but why does everyone in the embedded space seem to be using gcc-4.4 instead of newer releases. I'm sure there must be a reason. I feel like I missed the memo :) |
| # 18:55:24 | alan_o | And don't get me wrong, I'm not complaining :) |
| # 19:00:12 | kos_tom | alan_o: where did you get that everybody using 4.4 ? |
| # 19:00:19 | kos_tom | Linaro has 4.5 and 4.6 based toolchains |
| # 19:00:23 | kos_tom | some other people are using 4.3 |
| # 19:00:33 | kos_tom | and I'm pretty sure there are still people using 3.x gcc releases. |
| # 19:03:35 | y_morin | alan_o, kos_tom: I do still use a gcc-3 toolchain for an exotic MIPS variant. :-/ |
| # 19:04:35 | y_morin | alan_o: it all depends what you mean by "everybody". If you get your toolchain from a chip vendor, then they probably do not want to upgrade. |
| # 19:05:04 | y_morin | alan_o: but if you refer to people building their own toolchains, as kos_tom said, many people are using more up-to-date gcc nowadays. |
| # 19:05:43 | y_morin | Especially in the ARM world, where Linaro is doing quite a good work at working on the ARM support. :-) |
| # 19:06:05 | alan_o | okok, maybe not everybody |
| # 19:06:15 | alan_o | that was a bit of an exaggeration I suppose :) |
| # 19:06:43 | alan_o | I've seen it a few places though and it seemed to indicate a pattern. I guess the answer is that I was wrong and there is no pattern. |
| # 19:07:11 | y_morin | alan_o: yes :-) But fact is, in industrial context, updating the toolchain is a very risky task. So, projects tend to stick with a known-working-even-if-not-optimal toolchain for as long as they do not find a bug... |
| # 19:07:27 | alan_o | sure, absolutely |
| # 19:07:33 | y_morin | Which can span a few years... |
| # 19:08:07 | y_morin | In the community, it's quite the opposite: upgrade asap, and keep the pieces together! :-) |
| # 19:08:10 | y_morin | is getting a bit hungry, and goes make some burgers! Hmmm! :-) |
| # 19:08:40 | alan_o | woot, burgers! Thanks for the answers, guys |
| # 19:08:55 | ben1066 | quits : Remote host closed the connection |
| # 19:13:27 | kos_tom | alan_o: well, the thing is that gcc-4.4 is today a quite recent, but not too recent gcc versions. |
| # 19:13:44 | kos_tom | and for embedded archs, using a not too recent, but not too old gcc, is more or less the rule of thumb that everyone uses :) |
| # 19:27:45 | alan_o | kos_tom: Definitely sounds right. |
| # 21:18:08 | ben1066 | joins #crosstool-ng |
| # 21:18:09 | ben1066 | quits : Changing host |
| # 21:18:09 | ben1066 | joins #crosstool-ng |
| # 21:20:10 | ben1066 | quits : Read error: Connection reset by peer |
| # 21:21:57 | ben1066 | joins #crosstool-ng |
| # 21:21:58 | ben1066 | quits : Changing host |
| # 21:21:58 | ben1066 | joins #crosstool-ng |
| # 21:23:11 | ben1066 | quits : Read error: Connection reset by peer |
| # 21:24:36 | ben1066 | joins #crosstool-ng |
| # 21:24:37 | ben1066 | quits : Changing host |
| # 21:24:37 | ben1066 | joins #crosstool-ng |
| # 21:24:44 | smartin | quits |
| # 23:45:34 | y_morin | quits : Quit: Night! |