| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
|
| |
No need to keep filters and ifilters separately as we pass
them through with "filter=" and "ifilter=" intact.
|
|
|
|
|
| |
Needs tweaks within the cluster too, so don't try using
this immediately!
|
| |
|
| |
|
|
|
|
|
|
|
| |
With -p, if there is gap in 'Memory squeezing @ <N>' output (because of calls
to free()), output next <N>.
Also flush log output to avoid looking like we've hung.
|
|
|
|
| |
An alternative to squeeze2html.pl, outputing just summary information.
|
| |
|
| |
|
|
|
|
|
|
| |
And add it to the list of files to install on Unix systems.
Also, tweak the comments in pdf_info.ps to reflect its new home.
|
|
|
|
|
| |
.shellarguments for quite some time has thrown an undefined error if Ghostscript
is not invoked with the '--' option, so handle that.
|
|
|
|
|
|
| |
Mainly CIDFonts come up with multibyte characters in their names, hence making
the normal Postscript string pretty meaningless. This adds a hex string
representation which can be used in Fontmap.GS or cidfmap for subsitution.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug #701766 " genfontmap.ps Unrecoverable error, exit code 1"
The genfontmap.ps program, supplied as part of the support tools in
'toolbin' rather than Ghostscript proper, relies on the non-standard
PostScript extension operator '.sort'.
As part of the security hardening, as many non-standard operators as
possible were removed from Ghostscript when SAFER is set, including
.sort, and with version 9.50 SAFER becomes the default.
This commit simply updates the genfontmap.ps program to check that it
is being run with NOSAFER, emits a warning and exits if this is not the
case. Also update the comments to indicate why we are doing this.
|
|
|
|
|
| |
I never use binary output -- just -p for PostScript output, so this
was untested.
|
|
|
|
|
|
|
| |
Move the definition of x_pixel within the headers to ensure
gdevcmp.h stands alone.
Include a ufst header to ensure that gxfapiu.h stands alone.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
We ignore the bottom bytes of the pixel data.
|
|
|
|
|
|
|
|
|
|
| |
The loaders were passing an unitialise pointer into gsapi_new_instance()
meaning we might try to dereference the pointer to get to the shared portion
of the library context.
Initialise the pointer to NULL.
Apply the same fix to everywhere that uses gsapi_new_instance.
|
|
|
|
|
| |
This version doesn't assume there is a --oper-- form on the list, so
it works with "functions" (procedures) that as well as with operators.
|
|
|
|
|
|
| |
Also, the logic for "functions", which don't have the --oper-- form
on the whitelist, is currently broken, so just put everything
on the operator list until that's sorted (if ever).
|
|
|
|
| |
Not sure why the Ray's automated extraction didn't pick these up?
|
|
|
|
|
| |
This is in the PLRM, but it's not an operator and it's not going to
show up in the scan unless 'defineuserobject' has previously been run.
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is now an internal operator
Remove it from whitelist in scan_ps_dicts.ps
This has already been undef'd (after initialization), just fixing the
documentation.
This commit also adds a new "Internal.htm" documentation file, and
hopefully fixes up the links to it in Readme.htm
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
By setting the whitelist entry to //false initially, and the //true when
the operator is encountered in the scan, we can report elements that are in
the whitelist that probably don't need to be there (they've already been
undef'ed).
Also for operators, since they may be encountered in a dict in "bare" form,
or may be seen in packedarray procedures with "--" in front and back, we
check for either having been encountered by pulling out the "bare" form
and checking if that whitelist entry has been seen.
|
| |
|
| |
|
|
|
|
|
|
|
| |
- can break out the lists by category (standard vs extensions)
- adds the "--" around operators dynamically
- can put non-operators (functions) in a separate list if desired
- changed the value in the dict to //false
|
| |
|
| |
|
|
|
|
|
| |
- remove statusdict
- add some standard operators that aren't in the PLRM (related to color)
|
|
|
|
|
| |
Note that unfortunately, we have to have operators both in the 'bare'
form and the display form e.g. (exit) (--exit--).
|
| |
|
|
|
|
|
|
|
|
|
|
| |
1) I am using pngize=0. My version of bmpcmp automatically outputs in
png format. I think this reveals a bug related to file suffixes?
Anyway, I added an "outsuffix" variable and at least for my situation,
it now works. I don't know if this is a general fix or not.
2) The metafile string was built with $imstr, which isn't a defined
variable? Changed this to be $imstr1. How did this ever work?
|
|
|
|
|
|
|
|
| |
vdb.pl automates the running of valgrind jobs under gdb, and
multiplexes the output from valgrind and gdb together.
vgbatch.pl automates the running of a list of "cluster like"
tests under valgrind.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now we properly "include what we use" let's sanitise the horrid
blah_DEFINED ifdeffery (i.e. kill it where possible).
Also, we update the .c dependencies in the base/psi makefiles to
be correct.
Unfortunately, this new correct set of dependencies causes nmake
to soil itself and die with an out of memory error. After much
experimentation, I've come to the conclusion that this is because
it copes poorly with given the same file as a dependency multiple
times.
Sadly, our style of declaring dependencies in the following style:
foo_h=$(BLAH)/foo.h $(std_h)
bar_h=$(BLAH)/bar.h $(foo_h) $(std_h)
baz_h=$(BLAH)/baz.h $(foo_h) $(std_h)
means that a .obj file that depends on $(foo_h) $(bar_h) and $(baz_h)
ends up depending on foo.h twice, and std.h three times.
I have therefore changed the style of dependencies used to be more
standard.
We still define:
foo_h=$(BLAH)/foo.h
so each .obj file rule can depend on $(foo_h) etc as required, but the
dependencies between each .h file are expressed in normal rules at the
end of the file in a dedicated "# Dependencies" section that we can now
autogenerate.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This only removes operators that are DPS only. They are marked with
a "DPS" in the PLRM. Also removes related internal operators.
(gs_img.ps) Remove img_utils_dict
Dependency on gs_dps.ps is gone. Can just define the utility funcs for use
and then just undef them at end.
(gs_init.ps)
Don't need to undef dps operators anymore, because they won't be defined
(pdf_draw.ps)
Change PDF implementation to call .setscreenphase directly
This used to call it via the dps operator 'sethalftonephase', but that
is going away, so just make .setscreenphase be part of the pdf
implementation directly.
Also move implementation of .setscreenphase to zpdfops.c
(gs_cet.ps)
No longer need to undef 'deviceinfo' for CET because it won't be defined
(gs_btokn.ps)
Replace the DPS operators in .installsystemnames with placeholders
Keeps the length/values in the array the same, just removing dps operators.
(icontext.c)
Needed to modify the no_reschedule() proc to return 0 instead
of an error. I think we can delete a ton of related code, in future commit,
because the code handling the time_slice_proc and reschedule_proc should
no longer be needed.
(lots of changes)
Delete dps-related source files, update makefiles and other files that
reference the deleted files.
|
|
|
|
| |
Fix typo in output formatting and clean up a few warnings.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Run a release build on a linux machine to make arch.h etc. Then
run toolbin/headercompile.pl to test compiling each headerfile
by itself.
Resolve all the missing #includes, add missing repeated include
guards and copyright statements.
Also, update all the header dependencies in the makefiles.
It is possible that the object dependencies in the makefiles can be
simplified now, but that's a task for another day.
|
| |
|
| |
|