Re: webpage problem

[craig@jcb-sc.com]

[Back to egcs-bugs, regarding strange results viewing the gcc_2.html
page in onlinedocs with Netscape or MSIE under WNT.]

>     Don't recognize builtin functions that do not begin with `__builtin_'
>as prefix. Currently, the functions affected
>     include abort, abs, aoon allocaabort__typeorror standarGCCP> 
>====>
>     evopt+ c-heSTRICT_ANE="IDX36"> +
>     cgro40">behanabrE="IDX15 `-ansi' Don't
>     recognize M__tyP> as pref Hocess E="IDX36">
>     `-fn4>. 
>ly , the assetakNAMEed soDE>_ ction . You ction

Wow, well, here's the HTML I get via:

  lynx -dump -source http://egcs.cygnus.com/onlinedocs/gcc_2.html > incoming/gcc_2.html

>Don't recognize builtin functions that do not begin with <SAMP>`__builtin_'</SAMP>
>as prefix.  Currently, the functions affected include <CODE>abort</CODE>,
><CODE>abs</CODE>, <CODE>alloca</CODE>, <CODE>cos</CODE>, <CODE>exit</CODE>, <CODE>fabs</CODE>,
><CODE>ffs</CODE>, <CODE>labs</CODE>, <CODE>memcmp</CODE>, <CODE>memcpy</CODE>, <CODE>sin</CODE>,
><CODE>sqrt</CODE>, <CODE>strcmp</CODE>, <CODE>strcpy</CODE>, and <CODE>strlen</CODE>.

I don't see anything wrong with the HTML in that area.

Looks like you've got something wrong on your box somewhere, resulting
in garbage in the incoming HTML file as seen by the two browsers (which
definitely should *not* agree on how to screw up this file, so I don't
blame *both* of them).  Though (as always) it *might* conceivably be upstream,
of course.

The only other thing I could see wrong (via weblint) was empty <A> anchors.
Maybe both MSIE and Netscape trip up on those, but they'd both have to
do so in *very* subtle ways to account for the problem you're seeing.

I think I'll email a relative of mine at MS and ask her what she can
make of it.  (She works on MSIE.)

        tq vm, (burley)