Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(121)

Side by Side Diff: third_party/libjpeg/fpdfapi_jcapimin.c

Issue 1433803002: Get rid of _FX_JPEG_TURBO_ (Closed) Base URL: https://pdfium.googlesource.com/pdfium@master
Patch Set: Created 5 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « no previous file | third_party/libjpeg/fpdfapi_jcapistd.c » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 #if !defined(_FX_JPEG_TURBO_)
2 /* 1 /*
3 * jcapimin.c 2 * jcapimin.c
4 * 3 *
5 * Copyright (C) 1994-1998, Thomas G. Lane. 4 * Copyright (C) 1994-1998, Thomas G. Lane.
6 * This file is part of the Independent JPEG Group's software. 5 * This file is part of the Independent JPEG Group's software.
7 * For conditions of distribution and use, see the accompanying README file. 6 * For conditions of distribution and use, see the accompanying README file.
8 * 7 *
9 * This file contains application interface code for the compression half 8 * This file contains application interface code for the compression half
10 * of the JPEG library. These are the "minimum" API routines that may be 9 * of the JPEG library. These are the "minimum" API routines that may be
11 * needed in either the normal full-compression case or the transcoding-only 10 * needed in either the normal full-compression case or the transcoding-only
(...skipping 260 matching lines...) Expand 10 before | Expand all | Expand 10 after
272 * writer. Some applications had a problem with that: they allocated space 271 * writer. Some applications had a problem with that: they allocated space
273 * of their own from the library memory manager, and didn't want it to go 272 * of their own from the library memory manager, and didn't want it to go
274 * away during write_tables. So now we do nothing. This will cause a 273 * away during write_tables. So now we do nothing. This will cause a
275 * memory leak if an app calls write_tables repeatedly without doing a full 274 * memory leak if an app calls write_tables repeatedly without doing a full
276 * compression cycle or otherwise resetting the JPEG object. However, that 275 * compression cycle or otherwise resetting the JPEG object. However, that
277 * seems less bad than unexpectedly freeing memory in the normal case. 276 * seems less bad than unexpectedly freeing memory in the normal case.
278 * An app that prefers the old behavior can call jpeg_abort for itself after 277 * An app that prefers the old behavior can call jpeg_abort for itself after
279 * each call to jpeg_write_tables(). 278 * each call to jpeg_write_tables().
280 */ 279 */
281 } 280 }
282
283 #endif //_FX_JPEG_TURBO_
OLDNEW
« no previous file with comments | « no previous file | third_party/libjpeg/fpdfapi_jcapistd.c » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698