From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 6c CMP reg, $0 optimization
Date: Sat, 29 Mar 2014 00:12:35 -0400 [thread overview]
Message-ID: <2aea4cff3b5b2e59615eec9e436da834@brasstown.quanstro.net> (raw)
In-Reply-To: <ff5c718153cac25d07ef9c09ba6ca16d@felloff.net>
On Sat Mar 29 00:08:06 EDT 2014, cinap_lenrek@felloff.net wrote:
> what? i'm having no issues with ghostscript on amd64.
> do you have issues with some specific documents? the
> ones in /sys/doc work fine for me.
any intel datasheet, for example this one works on arm, mips
- erik
---
; page 82574.pdf # google 82574 datasheet
reading through pdf...
Ghostscript Error:
Error: /undefined in --setcolor--
Operand stack:
--dict:7/7(L)-- (Order) 0 0 0 --nostringval-- --nostringval-- cs_prepare_color --dict:13/20(G)-- --nostringval--
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostringval-- %array_continue --nostringval-- false 1 %stopped_push --nostringval-- %loop_continue --nostringval-- --nostringval-- --nostringvafatal: readimage error
l-- %array_continue --nostringval-- --nostringval-- 6 8 %oparray_pop
Dictionary stack:
--dict:1127/1686(ro)(G)-- --dict:2/20(G)-- --dict:78/200(L)-- --dict:105/127(ro)(G)-- --dict:258/347(ro)(G)-- --dict:21/24(L)-- --dict:4/6(L)-- --dict:25/32(L)--
Current allocation mode is local
next prev parent reply other threads:[~2014-03-29 4:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-29 3:56 cinap_lenrek
2014-03-29 4:00 ` erik quanstrom
2014-03-29 4:06 ` cinap_lenrek
2014-03-29 4:12 ` erik quanstrom [this message]
2014-03-29 4:12 ` Charles Forsyth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2aea4cff3b5b2e59615eec9e436da834@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).