Bug 97584
| Summary: | [Qt][meta] LLInt specific release critical bugs | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Csaba Osztrogonác <ossy> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | hausmann, ossy |
| Priority: | P2 | Keywords: | Qt, QtTriaged |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | 95749, 97586, 97587, 97589, 97648, 101159 | ||
| Bug Blocks: | |||
Csaba Osztrogonác
SSIA
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Simon Hausmann
Removing this bug from the Qt 5.0 blocker list. At this point we use LLInt-C-Loop only on Windows 64-bit (where it'll be a documented known issue) and ARM traditional seems to be falling behind :(
That said, if fixes make it into trunk in time, that's good. But I don't think those two should stop the entire release of Qt 5.0.0 (which depends on the WebKit issues tracked in bug #76773)
Jocelyn Turcotte
=== Bulk closing of Qt bugs ===
If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary.
If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.