Note that it takes like 24 hours for a bug to show up on bugs.sun.com
On Mon, 26 Mar 2007, Chris Quenelle wrote:
FYI:
Sun Studio bugs are private by default. You can add a "jdcinclude"
to make them public, but it's a manual process. Some Sun Studio
bugs refer to competitive information about SPEC benchmarks, or upcoming
hardware and we can't open those ones.
--chris
Alan Coopersmith wrote:
Al Hopper wrote:
On Sun, 25 Mar 2007, Peter Memishian wrote:
> I would like to propose a project aimed to improve ON build times.
This
> can live either under tools or under performance or under some
other
> community.
>
> There was some discussion about it a while ago in the context of
Google
> summer of code:
> http://www.opensolaris.org/jive/message.jspa?messageID=33951
While I certainly support the initiative, I'd like to hear a bit more
about what's planned. For instance, the earlier thread talked mainly
about parallelizing the build, but in my experience, a lot of the time
is
wasted because of bad algorithms inside the tools themselves rather
than
lack of parallelism. For instance, 6357412 showed how an undersized
hash
^^^^^^^
Sun internal only access?
It's a lint bug - lint is part of the Sun Studio compiler suite, which is
not open.
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
