Re: [webkit-dev] Ports not building as C++11?
Hi, On 07/26/2013 06:04 PM, Anders Carlsson wrote: Hi everyone, when Oliver landed his “let’s break everything” patches in JSC the other day, I noticed that some of the follow-up build fixes by other ports were removing use of C++11 features (mainly nullptr). Are there any ports that aren’t building as C++11? If so, why not? - Anders No, I don't have objections. :) I absolutely support switching to c++11, and I'm happy to add back the removed nullptrs and scoped enum values _after_ all ports switched to c++11. - cmake port did the switch by http://trac.webkit.org/changeset/153315 - GTK did the switch by http://trac.webkit.org/changeset/150445 - Qt and Win confirmed that they are going to do the switch, but I'm not sure if they already did it or not. Let the EWS bots notice us. :) Patch is coming soon in https://bugs.webkit.org/show_bug.cgi?id=119266 But I suprised how c++11 became mandatory. If you had announced it before pushing the FTL patches, we would have easily avoid the tons of buildfixes removing c++11 features. br, Ossy ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
Hi Patrick, On Jul 29, 2013, at 10:42 AM, Patrick East patri...@bsquare.com wrote: There is support for C++11 on Windows Embedded Compact 2013 using the newer VC11 compiler, but for CE 5, 6, or WEC 7 they will not be able to support it since they are limited to the VC9 compiler. Afaik there doesn’t appear to be any plans from Microsoft to back-port the newer compiler and run time to support older versions of CE. That’s too bad. Can you give me an idea of how big a ‘market’ we are talking about for these older OS releases? Are these targets likely to need or benefit from access to a ToT WebKit build? I realize that CE 5, 6, and 7 are probably not top priorities for the community, but these changes will basically force dropping support for those platforms. We do have some interest in keeping WebKit working for our downstream build, so if it’s possible to make this change over to using C++11 in a way that can allow for building without the new features that would be ideal. If there is anything we can do that help make this happen let me know. I think the goal is to (at least initially) conditionalize the use of various C++11 idioms. But I think we will soon reach a critical mass where we will assume the compiler supports the newer language constructs. -Brent ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
On Jul 30, 2013, at 9:23 AM, Osztrogonác Csaba o...@inf.u-szeged.hu wrote: No, I don't have objections. :) I absolutely support switching to c++11, and I'm happy to add back the removed nullptrs and scoped enum values _after_ all ports switched to c++11. - cmake port did the switch by http://trac.webkit.org/changeset/153315 - GTK did the switch by http://trac.webkit.org/changeset/150445 - Qt and Win confirmed that they are going to do the switch, but I'm not sure if they already did it or not. Let the EWS bots notice us. :) Patch is coming soon in https://bugs.webkit.org/show_bug.cgi?id=119266 Excellent! But I suprised how c++11 became mandatory. If you had announced it before pushing the FTL patches, we would have easily avoid the tons of buildfixes removing c++11 features. To clarify, this decision isn’t final yet - and has not yet been announced. I sent this e-mail because I was under the impression that most/all ports were already building as C++11 and it came a surprise to find that this was not the case. Regards, - Anders ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
On Jul 30, 2013, at 10:52 AM, Brent Fulgham bfulg...@apple.com wrote: I realize that CE 5, 6, and 7 are probably not top priorities for the community, but these changes will basically force dropping support for those platforms. We do have some interest in keeping WebKit working for our downstream build, so if it’s possible to make this change over to using C++11 in a way that can allow for building without the new features that would be ideal. If there is anything we can do that help make this happen let me know. I think the goal is to (at least initially) conditionalize the use of various C++11 idioms. But I think we will soon reach a critical mass where we will assume the compiler supports the newer language constructs. We’re already using C++11 features conditionally in WebKit. The plan is to move forward and make some features a requirement. Patrick, given the broad support for this proposal from other ports/contributors we are going to ahead and move forward with it. Regards, - Anders ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
Hi Brent, For a ballpark of the market size we have customers with millions of devices, and we believe there are several million other WinCE devices that are also utilizing WebKit. The target platforms do benefit quite a bit having access to the latest builds, nearly all of our customers push for having the latest performance enhancements, features, and bug fixes. Patrick East | Software Engineer +1 425.519.5912 | patri...@bsquare.commailto:patri...@bsquare.com Bsquare │Forging Smart Connections www.bsquare.comhttp://www.bsquare.com/ From: Brent Fulgham [mailto:bfulg...@apple.com] Sent: Tuesday, July 30, 2013 10:53 AM To: Patrick East Cc: Anders Carlsson; WebKit Development Subject: Re: [webkit-dev] Ports not building as C++11? Hi Patrick, On Jul 29, 2013, at 10:42 AM, Patrick East patri...@bsquare.commailto:patri...@bsquare.com wrote: There is support for C++11 on Windows Embedded Compact 2013 using the newer VC11 compiler, but for CE 5, 6, or WEC 7 they will not be able to support it since they are limited to the VC9 compiler. Afaik there doesn't appear to be any plans from Microsoft to back-port the newer compiler and run time to support older versions of CE. That's too bad. Can you give me an idea of how big a 'market' we are talking about for these older OS releases? Are these targets likely to need or benefit from access to a ToT WebKit build? I realize that CE 5, 6, and 7 are probably not top priorities for the community, but these changes will basically force dropping support for those platforms. We do have some interest in keeping WebKit working for our downstream build, so if it's possible to make this change over to using C++11 in a way that can allow for building without the new features that would be ideal. If there is anything we can do that help make this happen let me know. I think the goal is to (at least initially) conditionalize the use of various C++11 idioms. But I think we will soon reach a critical mass where we will assume the compiler supports the newer language constructs. -Brent ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
Thanks Anders. I look forward to the changes for our WEC2013 builds! Patrick East | Software Engineer +1 425.519.5912 | patri...@bsquare.commailto:patri...@bsquare.com Bsquare │Forging Smart Connections www.bsquare.comhttp://www.bsquare.com/ From: Anders Carlsson [mailto:ander...@apple.com] Sent: Tuesday, July 30, 2013 2:02 PM To: Brent Fulgham Cc: Patrick East; WebKit Development Subject: Re: [webkit-dev] Ports not building as C++11? On Jul 30, 2013, at 10:52 AM, Brent Fulgham bfulg...@apple.commailto:bfulg...@apple.com wrote: I realize that CE 5, 6, and 7 are probably not top priorities for the community, but these changes will basically force dropping support for those platforms. We do have some interest in keeping WebKit working for our downstream build, so if it's possible to make this change over to using C++11 in a way that can allow for building without the new features that would be ideal. If there is anything we can do that help make this happen let me know. I think the goal is to (at least initially) conditionalize the use of various C++11 idioms. But I think we will soon reach a critical mass where we will assume the compiler supports the newer language constructs. We're already using C++11 features conditionally in WebKit. The plan is to move forward and make some features a requirement. Patrick, given the broad support for this proposal from other ports/contributors we are going to ahead and move forward with it. Regards, - Anders ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
I’d really like to use atomic, which isn’t supported until VS2012. When will we VS2012? Geoff On Jul 28, 2013, at 9:10 PM, Brent Fulgham bfulg...@gmail.com wrote: We can support auto and move semantics. We cannot support ranged iterators until VS2012. But at least it's a step in the right direction... Sent from my iPad On Jul 28, 2013, at 2:36 PM, Oliver Hunt oli...@apple.com wrote: So wait, is everyone using C++11 now? I dream of using auto… :-D On Jul 28, 2013, at 12:47 PM, Gergely Kis gerg...@homejinni.com wrote: Hi, On Sun, Jul 28, 2013 at 7:30 PM, Allan Sandfeld Jensen k...@carewolf.com wrote: became required in WebKit2. The only fallout will likely be the loss of the Qt MIPS bot which is maintained by a third party and is too old. The MIPS bot was updated to Debian Wheezy and GCC 4.7.2 a few weeks ago, I just forgot to update the buildbot slave info file, did it now. Best Regards, Gergely the 3rd party maintaining the MIPS bot :) ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
FWIW the GTK+ port also builds with C++11 support. Philippe On Fri, 2013-07-26 at 09:04 -0700, Anders Carlsson wrote: Hi everyone, when Oliver landed his “let’s break everything” patches in JSC the other day, I noticed that some of the follow-up build fixes by other ports were removing use of C++11 features (mainly nullptr). Are there any ports that aren’t building as C++11? If so, why not? - Anders ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
Hi all, I'm afraid that our sh4 bot won't handle C++11 properly : http://build.webkit.org/builders/Qt%20Linux%20SH4%20Release $ sh4-linux-g++ --version sh4-linux-g++ (GCC) 4.6.3 20120613 (STMicroelectronics/Linux Base 4.6.3-111) Copyright (C) 2011 Free Software Foundation, Inc. Julien De : webkit-dev-boun...@lists.webkit.org [mailto:webkit-dev-boun...@lists.webkit.org] De la part de Geoffrey Garen Envoyé : lundi 29 juillet 2013 09:19 À : Brent Fulgham Cc : WebKit Development Objet : Re: [webkit-dev] Ports not building as C++11? I'd really like to use atomic, which isn't supported until VS2012. When will we VS2012? Geoff On Jul 28, 2013, at 9:10 PM, Brent Fulgham bfulg...@gmail.commailto:bfulg...@gmail.com wrote: We can support auto and move semantics. We cannot support ranged iterators until VS2012. But at least it's a step in the right direction... Sent from my iPad On Jul 28, 2013, at 2:36 PM, Oliver Hunt oli...@apple.commailto:oli...@apple.com wrote: So wait, is everyone using C++11 now? I dream of using auto... :-D On Jul 28, 2013, at 12:47 PM, Gergely Kis gerg...@homejinni.commailto:gerg...@homejinni.com wrote: Hi, On Sun, Jul 28, 2013 at 7:30 PM, Allan Sandfeld Jensen k...@carewolf.commailto:k...@carewolf.com wrote: became required in WebKit2. The only fallout will likely be the loss of the Qt MIPS bot which is maintained by a third party and is too old. The MIPS bot was updated to Debian Wheezy and GCC 4.7.2 a few weeks ago, I just forgot to update the buildbot slave info file, did it now. Best Regards, Gergely the 3rd party maintaining the MIPS bot :) ___ webkit-dev mailing list webkit-dev@lists.webkit.orgmailto:webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.orgmailto:webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.orgmailto:webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. An NDS Group Limited company. www.nds.com ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
On 07/29/2013 04:38 AM, Brianceau, Julien wrote: Hi all, I’m afraid that our sh4 bot won’t handle C++11 properly : http://build.webkit.org/builders/Qt%20Linux%20SH4%20Release $ sh4-linux-g++ --version sh4-linux-g++ (GCC) 4.6.3 20120613 (STMicroelectronics/Linux Base 4.6.3-111) Copyright (C) 2011 Free Software Foundation, Inc. For most of the thing this wont be a problem. http://gcc.gnu.org/gcc-4.6/cxx0x_status.html Julien *De :*webkit-dev-boun...@lists.webkit.org [mailto:webkit-dev-boun...@lists.webkit.org] *De la part de* Geoffrey Garen *Envoyé :* lundi 29 juillet 2013 09:19 *À :* Brent Fulgham *Cc :* WebKit Development *Objet :* Re: [webkit-dev] Ports not building as C++11? I’d really like to use atomic, which isn’t supported until VS2012. When will we VS2012? Geoff On Jul 28, 2013, at 9:10 PM, Brent Fulgham bfulg...@gmail.com mailto:bfulg...@gmail.com wrote: We can support auto and move semantics. We cannot support ranged iterators until VS2012. But at least it's a step in the right direction... Sent from my iPad On Jul 28, 2013, at 2:36 PM, Oliver Hunt oli...@apple.com mailto:oli...@apple.com wrote: So wait, is everyone using C++11 now? I dream of using auto… :-D On Jul 28, 2013, at 12:47 PM, Gergely Kis gerg...@homejinni.com mailto:gerg...@homejinni.com wrote: Hi, On Sun, Jul 28, 2013 at 7:30 PM, Allan Sandfeld Jensen k...@carewolf.com mailto:k...@carewolf.com wrote: became required in WebKit2. The only fallout will likely be the loss of the Qt MIPS bot which is maintained by a third party and is too old. The MIPS bot was updated to Debian Wheezy and GCC 4.7.2 a few weeks ago, I just forgot to update the buildbot slave info file, did it now. Best Regards, Gergely the 3rd party maintaining the MIPS bot :) ___ webkit-dev mailing list webkit-dev@lists.webkit.org mailto:webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org mailto:webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org mailto:webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. An NDS Group Limited company. www.nds.com ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
Hello, so it looks like we’re in a pretty decent shape when it comes to C++11 capable compilers. If we limit ourselves to GCC 4.6, MSVC 2010 and a fairly recent version of clang (Whatever comes with Xcode 4.6), we should be able to make use of a nice chunk of C++11 features. (See http://wiki.apache.org/stdcxx/C%2B%2B0xCompilerSupport for more details). I think a good set of initial features to require is auto, nullptr, move semantics and not having to add a space after angle brackets in templates. Unless anyone objects, I’ll prepare a patch for Compiler.h that adds the correct WTF_COMPILER_SUPPORTS #ifdefs, and adds an #error if any of WTF_COMPILER_SUPPORTS_CXX_AUTO, WTF_COMPILER_SUPPORTS_CXX_NULLPTR, WTF_COMPILER_SUPPORTS_CXX_RVALUE_REFERENCES are not defined. Regards, - Anders ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
There is support for C++11 on Windows Embedded Compact 2013 using the newer VC11 compiler, but for CE 5, 6, or WEC 7 they will not be able to support it since they are limited to the VC9 compiler. Afaik there doesn’t appear to be any plans from Microsoft to back-port the newer compiler and run time to support older versions of CE. I realize that CE 5, 6, and 7 are probably not top priorities for the community, but these changes will basically force dropping support for those platforms. We do have some interest in keeping WebKit working for our downstream build, so if it’s possible to make this change over to using C++11 in a way that can allow for building without the new features that would be ideal. If there is anything we can do that help make this happen let me know. Thanks! Patrick East | Software Engineer +1 425.519.5912 | patri...@bsquare.commailto:patri...@bsquare.com Bsquare │Forging Smart Connections www.bsquare.comhttp://www.bsquare.com/ From: webkit-dev-boun...@lists.webkit.org [mailto:webkit-dev-boun...@lists.webkit.org] On Behalf Of Brent Fulgham Sent: Saturday, July 27, 2013 3:04 PM To: Anders Carlsson Cc: WebKit Development Subject: Re: [webkit-dev] Ports not building as C++11? The only platform I know cannot support C++11 is WinCE, and that port is in favor of making the move to C++11 in anticipation of updated build tools from Microsoft. What other platform are we talking about here? The GNU compilers have supported C++11 for a long time. -Brent Sent from my iPhone On Jul 26, 2013, at 8:12 PM, Anders Carlsson ander...@apple.commailto:ander...@apple.com wrote: On Jul 26, 2013, at 8:09 PM, Allan Sandfeld Jensen k...@carewolf.commailto:k...@carewolf.com wrote: On Friday 26 July 2013, Anders Carlsson wrote: Hi everyone, when Oliver landed his “let’s break everything” patches in JSC the other day, I noticed that some of the follow-up build fixes by other ports were removing use of C++11 features (mainly nullptr). Are there any ports that aren’t building as C++11? If so, why not? Yes, and because C++11 is not supported on all the platforms we support. Could you please elaborate? What compilers are you using? We don't all have the option to not care about the platforms of a certain fruit themed vendor's 1 or 2 year old operating systems. I don’t think this comment adds anything constructive. Thanks, - Anders ___ webkit-dev mailing list webkit-dev@lists.webkit.orgmailto:webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
FYI: In gcc 4.7, things like foo%PRIuS are hard errors due to user-defined literals (it's a disablable warning in clang and gcc4.8, and gcc4.6 is fine since it doesn't implement user-defined literals yet), and some system headers (dbus1.0, dbus1.2, probably others) contain code like that. I'd encourage you to try actually building WebKit in c++11 mode with your port to check if you run into anything like that. Nico On Mon, Jul 29, 2013 at 10:42 AM, Patrick East patri...@bsquare.com wrote: There is support for C++11 on Windows Embedded Compact 2013 using the newer VC11 compiler, but for CE 5, 6, or WEC 7 they will not be able to support it since they are limited to the VC9 compiler. Afaik there doesn’t appear to be any plans from Microsoft to back-port the newer compiler and run time to support older versions of CE. ** ** I realize that CE 5, 6, and 7 are probably not top priorities for the community, but these changes will basically force dropping support for those platforms. We do have some interest in keeping WebKit working for our downstream build, so if it’s possible to make this change over to using C++11 in a way that can allow for building without the new features that would be ideal. If there is anything we can do that help make this happen let me know. ** ** Thanks! ** ** *Patrick East* | Software Engineer +1 425.519.5912 | patri...@bsquare.com Bsquare │Forging Smart Connections www.bsquare.com ** ** ** ** ** ** *From:* webkit-dev-boun...@lists.webkit.org [mailto: webkit-dev-boun...@lists.webkit.org] *On Behalf Of *Brent Fulgham *Sent:* Saturday, July 27, 2013 3:04 PM *To:* Anders Carlsson *Cc:* WebKit Development *Subject:* Re: [webkit-dev] Ports not building as C++11? ** ** The only platform I know cannot support C++11 is WinCE, and that port is in favor of making the move to C++11 in anticipation of updated build tools from Microsoft. ** ** What other platform are we talking about here? The GNU compilers have supported C++11 for a long time. ** ** -Brent Sent from my iPhone On Jul 26, 2013, at 8:12 PM, Anders Carlsson ander...@apple.com wrote:** ** ** ** On Jul 26, 2013, at 8:09 PM, Allan Sandfeld Jensen k...@carewolf.com wrote: On Friday 26 July 2013, Anders Carlsson wrote: Hi everyone, when Oliver landed his “let’s break everything” patches in JSC the other day, I noticed that some of the follow-up build fixes by other ports were removing use of C++11 features (mainly nullptr). Are there any ports that aren’t building as C++11? If so, why not? Yes, and because C++11 is not supported on all the platforms we support. * *** ** ** Could you please elaborate? What compilers are you using? We don't all have the option to not care about the platforms of a certain fruit themed vendor's 1 or 2 year old operating systems. ** ** I don’t think this comment adds anything constructive. ** ** Thanks, - Anders ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
On Saturday 27 July 2013, Allan Sandfeld Jensen wrote: On Friday 26 July 2013, Anders Carlsson wrote: Hi everyone, when Oliver landed his “let’s break everything” patches in JSC the other day, I noticed that some of the follow-up build fixes by other ports were removing use of C++11 features (mainly nullptr). Are there any ports that aren’t building as C++11? If so, why not? Yes, and because C++11 is not supported on all the platforms we support. We don't all have the option to not care about the platforms of a certain fruit themed vendor's 1 or 2 year old operating systems. I apologize for that comment. It was not meant seriously, and is much more antagonizing than funny, so please forget I ever wrote that. On a serious note, we have nothing blocking activating C++11 in the Qt port of WebKit. I prepared WTF and WebCore for C++11 with GCC months ago, and we dropped support for platforms where it isn't available from support when C++11 became required in WebKit2. The only fallout will likely be the loss of the Qt MIPS bot which is maintained by a third party and is too old. Regards `Allan ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
Hi, On Sun, Jul 28, 2013 at 7:30 PM, Allan Sandfeld Jensen k...@carewolf.com wrote: became required in WebKit2. The only fallout will likely be the loss of the Qt MIPS bot which is maintained by a third party and is too old. The MIPS bot was updated to Debian Wheezy and GCC 4.7.2 a few weeks ago, I just forgot to update the buildbot slave info file, did it now. Best Regards, Gergely the 3rd party maintaining the MIPS bot :) ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
So wait, is everyone using C++11 now? I dream of using auto… :-D On Jul 28, 2013, at 12:47 PM, Gergely Kis gerg...@homejinni.com wrote: Hi, On Sun, Jul 28, 2013 at 7:30 PM, Allan Sandfeld Jensen k...@carewolf.com wrote: became required in WebKit2. The only fallout will likely be the loss of the Qt MIPS bot which is maintained by a third party and is too old. The MIPS bot was updated to Debian Wheezy and GCC 4.7.2 a few weeks ago, I just forgot to update the buildbot slave info file, did it now. Best Regards, Gergely the 3rd party maintaining the MIPS bot :) ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
We can support auto and move semantics. We cannot support ranged iterators until VS2012. But at least it's a step in the right direction... Sent from my iPad On Jul 28, 2013, at 2:36 PM, Oliver Hunt oli...@apple.com wrote: So wait, is everyone using C++11 now? I dream of using auto… :-D On Jul 28, 2013, at 12:47 PM, Gergely Kis gerg...@homejinni.com wrote: Hi, On Sun, Jul 28, 2013 at 7:30 PM, Allan Sandfeld Jensen k...@carewolf.com wrote: became required in WebKit2. The only fallout will likely be the loss of the Qt MIPS bot which is maintained by a third party and is too old. The MIPS bot was updated to Debian Wheezy and GCC 4.7.2 a few weeks ago, I just forgot to update the buildbot slave info file, did it now. Best Regards, Gergely the 3rd party maintaining the MIPS bot :) ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
The only platform I know cannot support C++11 is WinCE, and that port is in favor of making the move to C++11 in anticipation of updated build tools from Microsoft. What other platform are we talking about here? The GNU compilers have supported C++11 for a long time. -Brent Sent from my iPhone On Jul 26, 2013, at 8:12 PM, Anders Carlsson ander...@apple.com wrote: On Jul 26, 2013, at 8:09 PM, Allan Sandfeld Jensen k...@carewolf.com wrote: On Friday 26 July 2013, Anders Carlsson wrote: Hi everyone, when Oliver landed his “let’s break everything” patches in JSC the other day, I noticed that some of the follow-up build fixes by other ports were removing use of C++11 features (mainly nullptr). Are there any ports that aren’t building as C++11? If so, why not? Yes, and because C++11 is not supported on all the platforms we support. Could you please elaborate? What compilers are you using? We don't all have the option to not care about the platforms of a certain fruit themed vendor's 1 or 2 year old operating systems. I don’t think this comment adds anything constructive. Thanks, - Anders ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
Hi, FYI, since Oliver's change, the EFL port is now building as C++11. Kr, Christophe DUMEZ. From: webkit-dev-boun...@lists.webkit.org [webkit-dev-boun...@lists.webkit.org] on behalf of Anders Carlsson [ander...@apple.com] Sent: Friday, July 26, 2013 19:04 To: webkit-dev@lists.webkit.org Subject: [webkit-dev] Ports not building as C++11? Hi everyone, when Oliver landed his “let’s break everything” patches in JSC the other day, I noticed that some of the follow-up build fixes by other ports were removing use of C++11 features (mainly nullptr). Are there any ports that aren’t building as C++11? If so, why not? - Anders ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
On Friday 26 July 2013, Anders Carlsson wrote: Hi everyone, when Oliver landed his “let’s break everything” patches in JSC the other day, I noticed that some of the follow-up build fixes by other ports were removing use of C++11 features (mainly nullptr). Are there any ports that aren’t building as C++11? If so, why not? Yes, and because C++11 is not supported on all the platforms we support. We don't all have the option to not care about the platforms of a certain fruit themed vendor's 1 or 2 year old operating systems. `Allan ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Ports not building as C++11?
On Jul 26, 2013, at 8:09 PM, Allan Sandfeld Jensen k...@carewolf.com wrote: On Friday 26 July 2013, Anders Carlsson wrote: Hi everyone, when Oliver landed his “let’s break everything” patches in JSC the other day, I noticed that some of the follow-up build fixes by other ports were removing use of C++11 features (mainly nullptr). Are there any ports that aren’t building as C++11? If so, why not? Yes, and because C++11 is not supported on all the platforms we support. Could you please elaborate? What compilers are you using? We don't all have the option to not care about the platforms of a certain fruit themed vendor's 1 or 2 year old operating systems. I don’t think this comment adds anything constructive. Thanks, - Anders___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
