[webkit-dev] Custom written css lexer
Hi, I am working on rewriting the css lexer, and someone suggested that it should be mentioned to a broader community, since we can drop the "flex" tool dependency from WebKit which affects all build systems. This mail is just a note, since the patch is not yet ready. https://bugs.webkit.org/show_bug.cgi?id=70107 Regards, Zoltan ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Removing support for the RVCT compiler
Yes, Blackberry uses RVCT (4.1 currently, so I believe 2.2 workarounds can be removed from our point of view.) > -Original Message- > From: webkit-dev-boun...@lists.webkit.org [mailto:webkit-dev- > boun...@lists.webkit.org] On Behalf Of Simon Hausmann > Sent: Monday, December 12, 2011 6:47 AM > To: webkit-dev@lists.webkit.org > Subject: Re: [webkit-dev] Removing support for the RVCT compiler > > On Sunday, December 11, 2011 02:55:40 AM ext Andreas Kling wrote: > > Hola WebKittens! > > > > Are there any objections to removing support for the RVCT compiler > (ARM > > RealView) in WebKit? As far as I know, the only user has been the > Symbian > > port which is no longer present on WebKit trunk. > > I believe some other folks (Brew? Blackberry?) have been compiling > WebKit with > RVCT. Generally speaking I think it's a pretty decent compiler provided > a > recent version is used. There are versions available for Linux for > example, so > it's not a Symbian specific compiler at all. > > The Qt builds were largely based on RVCT 2.2, which had its fair share > of > issues (not as bad as WINSCW though). I believe the majority of > compiler > workarounds in WebKit related to RVCT are because of this ancient > version. > > I think any RVCT related compiler workarounds could probably be > removed, > because there's a very high chance that they're due to 2.2. But I think > if > COMPILER(RVCT) is kept, then I can imagine that it would require very > little > maintenance to keep supporting it. > > (Interestingly enough grep in WebCore doesn't show anything RVCT > related, only > JavaScriptCore seems to have some serious workarounds for it) > > Simon > ___ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Removing support for the RVCT compiler
On Sunday, December 11, 2011 02:55:40 AM ext Andreas Kling wrote: > Hola WebKittens! > > Are there any objections to removing support for the RVCT compiler (ARM > RealView) in WebKit? As far as I know, the only user has been the Symbian > port which is no longer present on WebKit trunk. I believe some other folks (Brew? Blackberry?) have been compiling WebKit with RVCT. Generally speaking I think it's a pretty decent compiler provided a recent version is used. There are versions available for Linux for example, so it's not a Symbian specific compiler at all. The Qt builds were largely based on RVCT 2.2, which had its fair share of issues (not as bad as WINSCW though). I believe the majority of compiler workarounds in WebKit related to RVCT are because of this ancient version. I think any RVCT related compiler workarounds could probably be removed, because there's a very high chance that they're due to 2.2. But I think if COMPILER(RVCT) is kept, then I can imagine that it would require very little maintenance to keep supporting it. (Interestingly enough grep in WebCore doesn't show anything RVCT related, only JavaScriptCore seems to have some serious workarounds for it) Simon ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Arm conditional instructions support
Hi! "Condition cc=ALL" is the default function parameter in C++ (http://www.learncpp.com/cpp-tutorial/77-default-parameters/). There is no conditional instruction support in MacroAssembler level in SFX, but some lower-level optimizations use conditional execution. Regards, Zoltan > Hi! > I found that in > http://trac.webkit.org/browser/trunk/Source/JavaScriptCore/assembler/ARMAssembler.h > all functions were called with Condition cc=ALL parametr > Does it mean that SFX currently cannot support conditional execution? > -- > View this message in context: > http://old.nabble.com/Arm-conditional-instructions-support-tp32958547p32958547.html > Sent from the Webkit mailing list archive at Nabble.com. > > ___ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] Arm conditional instructions support
Hi! I found that in http://trac.webkit.org/browser/trunk/Source/JavaScriptCore/assembler/ARMAssembler.h all functions were called with Condition cc=ALL parametr Does it mean that SFX currently cannot support conditional execution? -- View this message in context: http://old.nabble.com/Arm-conditional-instructions-support-tp32958547p32958547.html Sent from the Webkit mailing list archive at Nabble.com. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] Fwd: How to OverLoad the new operator in webkit ?
FYI -- Forwarded message -- From: praveen munukutla Date: Mon, Dec 12, 2011 at 11:12 AM Subject: [webkit-dev] How to OverLoad the new operator in webkit ? To: zol...@webkit.org Hello Mr.Zoltan, Thanks for the response.We are using the webkit revision of 72805.So we are bound to use the Class version of FastAllocBase/Noncopyable . I have to implement the "placement new" for memory leaks.I have written the void* new(size_t,const char*,int) definition in the FastAllocBase.h -> NonCopyable -> page.For testing purpose im trying to call the placement new defined in the FastAllocBase from page. as int * p = new(__FILE__,__LINE__) int; which eventually should pick the void* new(size_t,const char*,int) but it not happening .I am getting linker errors as void* new(size_t,const char*,int) is undefined. any idea how to solve this ? Thanks , Praveen Message: 19 Date: Fri, 9 Dec 2011 16:48:15 +0530 From: praveen munukutla To: webkit-dev@lists.webkit.org Subject: [webkit-dev] How to OverLoad the new operator in webkit ? Message-ID: Content-Type: text/plain; charset="iso-8859-1" Hi all, How to OverLoad the new operator in webkit ? i have written an overloaded new operator void* operator new(size_t,int) in the FastAllocBase.h Fastallocbase is being inherited by Noncopyable and the Noncopyable is being inherited by class Page : public Noncopyable . now im calling int* p = new(1)int; in Page constructor. Page.cpp and FastAllocBase.h are complied but there is a problem in linking.I am getting a "undefined reference to operator new(unsigned int,int)" while linking time. Can anyone throw some light on this ? Thanks in advance. ~Praveen Munukutla. -- next part -- An HTML attachment was scrubbed... URL: < http://lists.webkit.org/pipermail/webkit-dev/attachments/20111209/81f96b98/attachment-0001.html > -- Message: 20 Date: Fri, 09 Dec 2011 12:33:24 +0200 From: "Zoltan Horvath" To: webkit-dev@lists.webkit.org Subject: Re: [webkit-dev] How to OverLoad the new operator in webkit ? Message-ID: Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes Hi, Noncopyable/FastAllocBase class doesn't exist anymore in WebKit, we turned them into macro implementations: http://trac.webkit.org/browser/trunk/Source/JavaScriptCore/wtf/FastAllocBase.h http://trac.webkit.org/browser/trunk/Source/JavaScriptCore/wtf/Noncopyable.h For primitive/POD types, you have to use FastNew to allocate and FastDelete to deallocate memory, please check it in FastAllocBase.h. Btw, new(1)int; ? Do you mean new int[1]? Regards, Zoltan Horvath -- ~Praveen Munukutla ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
