From: hjl@lucon.org (H.J. Lu)
To: egcs@cygnus.com
Subject: Another ppro bug
Date: Fri, 31 Oct 1997 17:23:00 -0000 [thread overview]
Message-ID: <m0xRSBl-0004ecC@ocean.lucon.org> (raw)
On linux/PPro,
# cc -S -O -march=i686 foo.cc
foo.cc: In method `class PlotFile3D & PlotFile3D::space(const class Vec3D &, const class Vec3D &)':
foo.cc:45: Internal compiler error.
foo.cc:45: Please submit a full bug report to `egcs-bugs@cygnus.com'.
I think it may have something to do with fmov.
H.J.
----
class Vec3D
{
protected:
double n[3];
public:
double x() const;
double y() const;
double z() const;
};
const int umini = 0;
const int vmini = 0;
const int umaxi = 3120;
const int vmaxi = 3120;
const double margin = 0.9;
class PlotFile3D
{
protected:
Vec3D ul,vl,wl;
Vec3D ur,vr,wr;
double scale;
double uorig, vorig;
public:
PlotFile3D& space (const Vec3D& p0, const Vec3D& p1);
PlotFile3D& home();
};
PlotFile3D& PlotFile3D::space(const Vec3D& pt0, const Vec3D& pt1)
{
double umin = (pt0.x() * ul.x()) <? (pt0.x() * ur.x())
<? (pt1.x() * ul.x()) <? (pt1.x() * ur.x());
double umax = (pt0.x() * ul.x()) >? (pt0.x() * ur.x())
>? (pt1.x() * ul.x()) >? (pt1.x() * ur.x());
double vmin = (pt0.x() * vl.x()) <? (pt0.x() * vr.x())
<? (pt1.x() * vl.x()) <? (pt1.x() * vr.x());
double vmax = (pt0.x() * vl.x()) >? (pt0.x() * vr.x())
>? (pt1.x() * vl.x()) >? (pt1.x() * vr.x());
umin += (pt0.y() * ul.y()) <? (pt0.y() * ur.y())
<? (pt1.y() * ul.y()) <? (pt1.y() * ur.y());
umax += (pt0.y() * ul.y()) >? (pt0.y() * ur.y())
>? (pt1.y() * ul.y()) >? (pt1.y() * ur.y());
int pixwidth = umaxi - umini;
int pixheight = vmaxi - vmini;
uorig = 0.5 * (pixwidth - scale*(umin+umax));
vorig = 0.5 * (pixheight - scale*(vmin+vmax));
return home();
}
reply other threads:[~1997-10-31 17:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m0xRSBl-0004ecC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=egcs@cygnus.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).