summaryrefslogtreecommitdiffstats
path: root/third_party
Commit message (Collapse)AuthorAgeFilesLines
* GYP changes for FreeBSD and OpenBSDpvalchev@google.com2010-05-149-14/+21
| | | | | | Review URL: http://codereview.chromium.org/1480002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@47327 0039d316-1c4b-4281-b951-d872f2087c98
* remove last comma from enum lists (required to build on NaCl with stricter ↵nfullagar@google.com2010-05-141-5/+5
| | | | | | | | compiler) Review URL: http://codereview.chromium.org/2090005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@47302 0039d316-1c4b-4281-b951-d872f2087c98
* Fixed up several sscanf format strings/arguments to get rid of warnings. ↵dmaclach@chromium.org2010-05-149-1566/+1617
| | | | | | | | | | | | Also fixes up what looked like a potentially crashing bug. BUG=none TEST=none Review: http://codereview.chromium.org/2105001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@47296 0039d316-1c4b-4281-b951-d872f2087c98
* Commiting http://codereview.chromium.org/2017007/show on behalf of ↵zelidrag@chromium.org2010-05-141-1/+1
| | | | | | | | | | | | | | | | | | | | rkc@chromium.org. This change hooks issue report dialog with Google Feedback backend for ChromeOS. The dialog is going to be used only for Chrome OS at the moment, the previous mechanism is kept intact for other operating systems. Image and System Info reporting is disabled at the moment; for image, we need feedback to get their changes in production, for reporting, the system scripts need to be added (basic Chrome and OS version info is being sent with the report) BUG=chromium-os:2761 TEST=none, work in progress TBR=zelidrag Review URL: http://codereview.chromium.org/2068004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@47244 0039d316-1c4b-4281-b951-d872f2087c98
* More changes to sync npapi.h to the upstream npapi-headers version.stuartmorgan@chromium.org2010-05-131-67/+62
| | | | | | | | | | | | - Syncs the use of NP_LOADDS - Pulls recent minor upstream cleanup BUG=42645 TEST=None; no behavioral changes Review URL: http://codereview.chromium.org/2091003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@47219 0039d316-1c4b-4281-b951-d872f2087c98
* Removed non-thread-safe QName ad-hoc interning.akalin@chromium.org2010-05-135-313/+208
| | | | | | | | | BUG=43467 TEST=made sure sync_integration_tests don't have any more ~QName crashes Review URL: http://codereview.chromium.org/2012014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@47109 0039d316-1c4b-4281-b951-d872f2087c98
* Update the Pepper scrollbar widget to use the new WebKit Scrollbar interface.jam@chromium.org2010-05-121-4/+12
| | | | | | Review URL: http://codereview.chromium.org/2008008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@47000 0039d316-1c4b-4281-b951-d872f2087c98
* Added win-specific direct-dependent settings to libjingle.gyp.akalin@chromium.org2010-05-111-0/+8
| | | | | | | | | BUG=none TEST=trybots Review URL: http://codereview.chromium.org/2042010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46946 0039d316-1c4b-4281-b951-d872f2087c98
* Change npapi.h header guard to match npapi-headers versionstuartmorgan@chromium.org2010-05-111-3/+3
| | | | | | | | | BUG=42645 TEST=Everything still compiles Review URL: http://codereview.chromium.org/2002008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46927 0039d316-1c4b-4281-b951-d872f2087c98
* Add more OS/2 defines to npapi.hstuartmorgan@chromium.org2010-05-111-0/+43
| | | | | | | | | | | Brings us yet closer to matching the npapi-headers version. BUG=42645 TEST=None; no behavioral changes. Review URL: http://codereview.chromium.org/2014008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46918 0039d316-1c4b-4281-b951-d872f2087c98
* Reimplement accessibility of web content by caching the entire dmazzoni@chromium.org2010-05-112-0/+4305
| | | | | | | | | | | | | | | | | | | | | | | | | | accessibility tree in the browser process. Adds new RPCs for a browser tab to request accessibility info from a renderer; the renderer responds with a complete tree of accessibility metadata for the entire DOM, which is then cached in the RenderWidgetHostView. This part is cross-platform and will help with accessibility on both Windows and Mac OS X. For Windows, MSAA support for web content has been rewritten to use this new cache. Tested in JAWS and NVDA screen readers. Using Chrome with a screen reader is now fast and stable, unlike the previous implementation. However, note that most advanced functionality is still not supported, and much work remains to make Chrome work well with a screen reader. This is a necessary step to improve stability first. BUG=25564 BUG=13291 TEST=See http://codereview.chromium.org/1806001 Review URL: http://codereview.chromium.org/1637018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46916 0039d316-1c4b-4281-b951-d872f2087c98
* Update the vendor tcmalloc branch to r94.glider@chromium.org2010-05-1122-211/+394
| | | | | | | | | | This CL doesn't affect any Chromium code. TBD=willchan Review URL: http://codereview.chromium.org/2004007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46906 0039d316-1c4b-4281-b951-d872f2087c98
* Add Symbian defines to npapi.h to match upstream changesstuartmorgan@chromium.org2010-05-101-8/+16
| | | | | | | | | BUG=42645 TEST=None; no behavioral changes. Review URL: http://codereview.chromium.org/2015009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46871 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 46842 - Reimplement accessibility of web content by caching the entire dmazzoni@chromium.org2010-05-102-4304/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | accessibility tree in the browser process. Adds new RPCs for a browser tab to request accessibility info from a renderer; the renderer responds with a complete tree of accessibility metadata for the entire DOM, which is then cached in the RenderWidgetHostView. This part is crossplatform and will help with accessibility on both Windows and Mac OS X. For Windows, MSAA support for web content has been rewritten to use this new cache. Tested in JAWS and NVDA screen readers. Using Chrome with a screen reader is now fast and stable, unlike the previous implementation. However, note that most advanced functionality is still not supported, and much work remains to make Chrome work well with a screen reader. This is a necessary step to improve stability first. BUG=25564 BUG=13291 TEST=See http://codereview.chromium.org/1806001 Review URL: http://codereview.chromium.org/1637018 TBR=dmazzoni@chromium.org Review URL: http://codereview.chromium.org/1989009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46847 0039d316-1c4b-4281-b951-d872f2087c98
* Reimplement accessibility of web content by caching the entire dmazzoni@chromium.org2010-05-102-0/+4304
| | | | | | | | | | | | | | | | | | | | | | | | | | accessibility tree in the browser process. Adds new RPCs for a browser tab to request accessibility info from a renderer; the renderer responds with a complete tree of accessibility metadata for the entire DOM, which is then cached in the RenderWidgetHostView. This part is cross-platform and will help with accessibility on both Windows and Mac OS X. For Windows, MSAA support for web content has been rewritten to use this new cache. Tested in JAWS and NVDA screen readers. Using Chrome with a screen reader is now fast and stable, unlike the previous implementation. However, note that most advanced functionality is still not supported, and much work remains to make Chrome work well with a screen reader. This is a necessary step to improve stability first. BUG=25564 BUG=13291 TEST=See http://codereview.chromium.org/1806001 Review URL: http://codereview.chromium.org/1637018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46842 0039d316-1c4b-4281-b951-d872f2087c98
* Switch to using npfunctions.h from npapi-headers for NPAPI declarationsstuartmorgan@chromium.org2010-05-103-289/+227
| | | | | | | | | BUG=42645 TEST=Compiling still works. Review URL: http://codereview.chromium.org/2003009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46814 0039d316-1c4b-4281-b951-d872f2087c98
* Add parameters to CreateWidget Pepper API so we can specify whether a ↵jam@chromium.org2010-05-071-3/+8
| | | | | | | | scrollbar is vertical or not. Review URL: http://codereview.chromium.org/1996009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46741 0039d316-1c4b-4281-b951-d872f2087c98
* Remove the obsolete JRI bits from the NPAPI headersstuartmorgan@chromium.org2010-05-072-14/+1
| | | | | | | | | BUG=42645 TEST=Existing plugin tests continue to pass; nothing should change. Review URL: http://codereview.chromium.org/2011005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46732 0039d316-1c4b-4281-b951-d872f2087c98
* Add new widget API to Pepper to replace the old theming API. The ↵jam@chromium.org2010-05-071-184/+222
| | | | | | | | implementation is a copy of the WebKit code, I will figure out how to reuse it soon. Review URL: http://codereview.chromium.org/2011004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46710 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 46567 - Reimplement accessibility of web content by caching the entire zork@chromium.org2010-05-072-4304/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | accessibility tree in the browser process. Adds new RPCs for a browser tab to request accessibility info from a renderer; the renderer responds with a complete tree of accessibility metadata for the entire DOM, which is then cached in the RenderWidgetHostView. This part is crossplatform and will help with accessibility on both Windows and Mac OS X. For Windows, MSAA support for web content has been rewritten to use this new cache. Tested in JAWS and NVDA screen readers. Using Chrome with a screen reader is now fast and stable, unlike the previous implementation. However, note that most advanced functionality is still not supported, and much work remains to make Chrome work well with a screen reader. This is a necessary step to improve stability first. BUG=25564 BUG=13291 TEST=See http://codereview.chromium.org/1806001 Review URL: http://codereview.chromium.org/1637018 TBR=dmazzoni@chromium.org Review URL: http://codereview.chromium.org/2031004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46642 0039d316-1c4b-4281-b951-d872f2087c98
* Bring npapi.h closer to the npapi-headers project versionstuartmorgan@chromium.org2010-05-061-87/+100
| | | | | | | | | | | | | | | | | | | This makes a bunch of changes that shouldn't actually affect anything: - Removes XP_MAC - Removes old Carbon event constants - Removes Metrowerks defines - Adds new constants and structs from recent spec updates - Adds OS/2 defines - Adds Maemo defines Also makes more whitespace adjustments to track central repository. BUG=42645 TEST=none; no behavioral changes Review URL: http://codereview.chromium.org/1995007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46596 0039d316-1c4b-4281-b951-d872f2087c98
* Reimplement accessibility of web content by caching the entire dmazzoni@chromium.org2010-05-062-0/+4304
| | | | | | | | | | | | | | | | | | | | | | | | | | accessibility tree in the browser process. Adds new RPCs for a browser tab to request accessibility info from a renderer; the renderer responds with a complete tree of accessibility metadata for the entire DOM, which is then cached in the RenderWidgetHostView. This part is cross-platform and will help with accessibility on both Windows and Mac OS X. For Windows, MSAA support for web content has been rewritten to use this new cache. Tested in JAWS and NVDA screen readers. Using Chrome with a screen reader is now fast and stable, unlike the previous implementation. However, note that most advanced functionality is still not supported, and much work remains to make Chrome work well with a screen reader. This is a necessary step to improve stability first. BUG=25564 BUG=13291 TEST=See http://codereview.chromium.org/1806001 Review URL: http://codereview.chromium.org/1637018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46567 0039d316-1c4b-4281-b951-d872f2087c98
* Eliminate non-functional differences between our NPAPI headers and the ↵stuartmorgan@chromium.org2010-05-052-427/+408
| | | | | | | | | | | | | npapi-headers copies This changes only whitespace/comment and file order differences; substantive changes will be done separately. BUG=42645 TEST=None; no behavioral changes. Review URL: http://codereview.chromium.org/2001001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46522 0039d316-1c4b-4281-b951-d872f2087c98
* Move NPAPI to C99 typesstuartmorgan@chromium.org2010-05-056-113/+185
| | | | | | | | | BUG=42645 TEST=None; no behavioral change. Review URL: http://codereview.chromium.org/1910004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46463 0039d316-1c4b-4281-b951-d872f2087c98
* Fix -[NSString isValidURI].dcheng@chromium.org2010-05-042-3/+6
| | | | | | | | | | | | | Use GURL for validation instead of NSURL. NSURL is extremely liberal with what it considers a valid URI, since it also uses RFC 1808 to parse. BUG=43100 TEST=none Review URL: http://codereview.chromium.org/1904001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46318 0039d316-1c4b-4281-b951-d872f2087c98
* ffmpeg move a file from neon to arm section for build errorfbarchard@chromium.org2010-04-301-1/+1
| | | | | | | | | BUG=42845 TEST=arm chrome should build Review URL: http://codereview.chromium.org/1801009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46111 0039d316-1c4b-4281-b951-d872f2087c98
* ffmpeg configs for float pcmfbarchard@chromium.org2010-04-308-16/+16
| | | | | | | | | BUG=42861 TEST=http://fbarchard-kir.ad.corp.google.com/mediatests/sixmusictest-32float.wav should work with ffmpeg_tests, media_bench immediately. Other programs will require additional support. Review URL: http://codereview.chromium.org/1731022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46105 0039d316-1c4b-4281-b951-d872f2087c98
* Re-apply http://codereview.chromium.org/1622012timurrrr@chromium.org2010-04-303-0/+1255
| | | | | | | | | It was reverted as http://codereview.chromium.org/1822001 the fix in Valgrind scripts has been commited as http://codereview.chromium.org/1736026 TEST=trybots Review URL: http://codereview.chromium.org/1763023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46070 0039d316-1c4b-4281-b951-d872f2087c98
* Update the vendor tcmalloc to r93.glider@chromium.org2010-04-3051-1804/+6476
| | | | | | | TBR=willchan Review URL: http://codereview.chromium.org/1800011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46054 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "[Third time landing] Python implementation of sync server, for testing."phajdan.jr@chromium.org2010-04-303-1255/+0
| | | | | | | | | | This broke the memory waterfall, failed to import protobuf. TBR=nick Review URL: http://codereview.chromium.org/1822001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46048 0039d316-1c4b-4281-b951-d872f2087c98
* [Third time landing] Python implementation of sync server, for testing.nick@chromium.org2010-04-303-0/+1255
| | | | | | | | | | | | | | | | | | | | | | | | | | Implement the server side of chromium sync inside of testserver.py. The implementation supports at most one account (and ignores authentication credentials), but is otherwise reasonably full featured. Make the sync_integration_tests run by default against the test server. An externally-provided --sync-url will give the old behavior. Protocol buffers stuff: The test sync server requires Python generated code for .proto files. I've put generated code, as well as the python protocol buffers runtime library, in the output directory + "/python" (e.g, on windows, src/chrome/Debug/python/google/protobuf). Flakiness fix: In the InProcessBrowserTest framework, improve the mechanism for tests that want to manually set up a user data directory. The new way ensures that the user data directory is always wiped; tests can't accidentally forget to do this anymore. Flakiness fix: Make testserver try to /kill any old instance that might be hogging the port. Very useful if a test failure leaves a server running. Tested this against all combos of protocols, and it seems to work. Flakiness fix: Port sync_integration_tests to the out-of-process test runner. Flakiness fix: For IN_PROC_BROWSER_TESTS, don't run the test body if the setup triggered a fatal (ASSERT_) failure. BUG=20905,40980 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=44708 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=45916 Review URL: http://codereview.chromium.org/1622012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46040 0039d316-1c4b-4281-b951-d872f2087c98
* Added cacheinvalidation.gyp to build/all.gyp.akalin@chromium.org2010-04-301-2/+8
| | | | | | | | | BUG=34646 TEST=trybots Review URL: http://codereview.chromium.org/1747018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46030 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 45916 - Python implementation of sync server, for testing.nick@chromium.org2010-04-293-1255/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | Implement the server side of chromium sync inside of testserver.py. The implementation supports at most one account (and ignores authentication credentials), but is otherwise reasonably full featured. Make the sync_integration_tests run by default against the test server. An externallyprovided syncurl will give the old behavior. Protocol buffers stuff: The test sync server requires Python generated code for .proto files. I've put generated code, as well as the python protocol buffers runtime library, in the output directory + "/python" (e.g, on windows, src/chrome/Debug/python/google/protobuf). This might be a bad place, or a bad name open to suggestions. The main thing is that there will be runtime dependencies on it, so it didn't seem right to put it in obj/. Flakiness fix: In the InProcessBrowserTest framework, improve the mechanism for tests that want to manually set up a user data directory. The new way ensures that the user data directory is always wiped; tests can't accidentally forget to do this anymore. Flakiness fix: Make testserver try to /kill any old instance that might be hogging the port. Very useful if a test failure leaves a server running. Tested this against all combos of protocols, and it seems to work. Flakiness fix: Port sync_integration_tests to the outofprocess test runner. Flakiness fix: For IN_PROC_BROWSER_TESTS, don't run the test body if the setup triggered a fatal (ASSERT_) failure. BUG=20905,40980 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=44708 Review URL: http://codereview.chromium.org/1622012 TBR=nick@chromium.org git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45918 0039d316-1c4b-4281-b951-d872f2087c98
* Python implementation of sync server, for testing.nick@chromium.org2010-04-293-0/+1255
| | | | | | | | | | | | | | | | | | | | | | | | Implement the server side of chromium sync inside of testserver.py. The implementation supports at most one account (and ignores authentication credentials), but is otherwise reasonably full featured. Make the sync_integration_tests run by default against the test server. An externally-provided --sync-url will give the old behavior. Protocol buffers stuff: The test sync server requires Python generated code for .proto files. I've put generated code, as well as the python protocol buffers runtime library, in the output directory + "/python" (e.g, on windows, src/chrome/Debug/python/google/protobuf). This might be a bad place, or a bad name -- open to suggestions. The main thing is that there will be run-time dependencies on it, so it didn't seem right to put it in obj/. Flakiness fix: In the InProcessBrowserTest framework, improve the mechanism for tests that want to manually set up a user data directory. The new way ensures that the user data directory is always wiped; tests can't accidentally forget to do this anymore. Flakiness fix: Make testserver try to /kill any old instance that might be hogging the port. Very useful if a test failure leaves a server running. Tested this against all combos of protocols, and it seems to work. Flakiness fix: Port sync_integration_tests to the out-of-process test runner. Flakiness fix: For IN_PROC_BROWSER_TESTS, don't run the test body if the setup triggered a fatal (ASSERT_) failure. BUG=20905,40980 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=44708 Review URL: http://codereview.chromium.org/1622012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45916 0039d316-1c4b-4281-b951-d872f2087c98
* Merged in fixes for GLEW compile errors on linux.apatrick@chromium.org2010-04-281-2/+5
| | | | | | | | | | | | GLEW patch: http://glew.svn.sourceforge.net/viewvc/glew?view=rev&revision=596 GLEW bug: http://sourceforge.net/tracker/index.php?func=detail&aid=2992222&group_id=67586&atid=523274 TEST=trybots BUG=41039 Review URL: http://codereview.chromium.org/1727010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45827 0039d316-1c4b-4281-b951-d872f2087c98
* Rolled cacheinvalidation to @13.akalin@chromium.org2010-04-282-0/+4
| | | | | | | | | | | Also added 'License File:' line to README.chromium. BUG=34645 TEST=unittests, tools/licenses.py Review URL: http://codereview.chromium.org/1748012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45769 0039d316-1c4b-4281-b951-d872f2087c98
* linux: remove use_system_libxslt, instead use xml flagevan@chromium.org2010-04-281-3/+7
| | | | | | | | | | | | We have weird crashes when system_libxslt != system_libxml. Nobody has diagnosed them. We should just use one flag for both so people stop reporting problems with it. BUG=42487 Review URL: http://codereview.chromium.org/1695019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45766 0039d316-1c4b-4281-b951-d872f2087c98
* ffmpeg disable zlib explicitely in the configurationfbarchard@chromium.org2010-04-272-2/+2
| | | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/1733020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45733 0039d316-1c4b-4281-b951-d872f2087c98
* gyp: unify toolkit_views usageevan@chromium.org2010-04-271-2/+2
| | | | | | | | | | | Now that we can rely on toolkit_views to be set when appropriate, we can simplify a bunch of logic in gyp. TEST=compiles Review URL: http://codereview.chromium.org/1741010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45727 0039d316-1c4b-4281-b951-d872f2087c98
* Mac: Prevent an NSException from being thrown in -getURLs:andTitles:.viettrungluu@chromium.org2010-04-271-2/+3
| | | | | | | | | | | | | | | | | Code shouldn't assume that any given pasteboard type that is promised will actually be provided. This "fixes" bug 42420, though kind of incidentally. More importantly, it fixes a crasher. Possibly, this should be upstreamed back into Camino. BUG=42420 TEST=dragging a bookmarklet (e.g., at <http://delicious.com/help/bookmarklets>) from web content to the bookmark bar won't cause a crash Review URL: http://codereview.chromium.org/1750016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45697 0039d316-1c4b-4281-b951-d872f2087c98
* Windows OSMesa DLL only exports OSMesa functions.apatrick@chromium.org2010-04-264-7/+5
| | | | | | | | | | | | It no longer exports all the GL functions like glClear. These are bound by calling OSMesaGetProcAddress. glew no longer uses default mangled export name bind to OSMesaGetProcAddress. TEST=trybots, check the pepper 3d plugin demos still work on windows BUG=none Review URL: http://codereview.chromium.org/1743004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45618 0039d316-1c4b-4281-b951-d872f2087c98
* ffmpeg add mkv, remove bzlib and zlibfbarchard@chromium.org2010-04-2321-41/+41
| | | | | | | | BUG=42306, 42307 TEST=none git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45451 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 45438 - ffmpeg add mkv, remove bzlib and zlibfbarchard@chromium.org2010-04-2321-38/+38
| | | | | | | | | | | BUG=42306, 42307 TEST=none TBR=fbarchard@chromium.org Review URL: http://codereview.chromium.org/1751012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45439 0039d316-1c4b-4281-b951-d872f2087c98
* ffmpeg add mkv, remove bzlib and zlibfbarchard@chromium.org2010-04-2321-38/+38
| | | | | | | | BUG=42306, 42307 TEST=none git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45438 0039d316-1c4b-4281-b951-d872f2087c98
* Added Google Cache Invalidation library to DEPS and got it to compileakalin@chromium.org2010-04-239-0/+425
| | | | | | | | | | | | | | with the Chromium libraries. Added some override files to make it work, the biggest of which defines NewPermanentCallback() overrides that base/callback.h doesn't handle. BUG=34646 TEST=added unittests Review URL: http://codereview.chromium.org/1720001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45412 0039d316-1c4b-4281-b951-d872f2087c98
* Use the /INCLUDE:symbol linker option pragmas to forcewtc@chromium.org2010-04-231-7/+14
| | | | | | | | | | | | | | | | | | references to the magic variables we added to the data segment for TLS callbacks. The references prevent whole program optimization from optimizing away those variables. This requires three changes: 1) the variables cannot be declared as static. 2) the variables must be declared extern "C" to suppress C++ name mangling. 3) the variables cannot have the same name. R=jar,maruel BUG=40663 TEST=none Review URL: http://codereview.chromium.org/1752004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45405 0039d316-1c4b-4281-b951-d872f2087c98
* Revert r45389. Experiment over.willchan@chromium.org2010-04-231-1/+1
| | | | | | | | | Revert "TCMalloc: Experiment with setting FLAGS_tcmalloc_release_rate to 50. This is a performance / memory usage tradeoff. 50 is pretty high. I'm going to revert this after a run or two on the buildbots." BUG=28385 Review URL: http://codereview.chromium.org/1739003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45401 0039d316-1c4b-4281-b951-d872f2087c98
* TCMalloc: Experiment with setting FLAGS_tcmalloc_release_rate to 50. This ↵willchan@chromium.org2010-04-231-1/+1
| | | | | | | | | | is a performance / memory usage tradeoff. 50 is pretty high. I'm going to revert this after a run or two on the buildbots. BUG=28385 Review URL: http://codereview.chromium.org/1771002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45389 0039d316-1c4b-4281-b951-d872f2087c98
* Corrected inconsistent newlines in third_party/mesa/mesa.gyp.apatrick@chromium.org2010-04-221-411/+411
| | | | | | | | | TEST=none BUG=none Review URL: http://codereview.chromium.org/1689008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45350 0039d316-1c4b-4281-b951-d872f2087c98
* Windows bots build and use OSMesaapatrick@chromium.org2010-04-211-0/+451
| | | | | | | | | | | This is a software GL renderer that can be used by bots that do not have access to native GL. It will be used for running tests that use GL, such as Pepper 3D, WebGL and accelerated compositing. Only working on Windows so far. TEST=trybots BUG=none Review URL: http://codereview.chromium.org/1740001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45241 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-15 01:05:50 +0000