RE: [help-texinfo] Re: small font in gcc online docs
Hello Karl,
Thanks for your reply.
> >> I see in the HTML this is the code causing the small font:
> >>
> >> pre.smallexample { font-size:smaller }
>
> I don't know of any way to say "use a slightly smaller font" in
> HTML/CSS. That is, this is what CSS provides, afaik.
>
> The reason that the above css exists at all is because users requested
> that @smallexample (the Texinfo command in question) produce smaller
> output than the regular @example, including in HTML. (Like
> @smalldisplay, @smallformat, @smallisp, and now @smallquotation.)
> Personally I don't have strong feelings about it.
Perhaps GCC could use @example rather than @smallexample ?
Does @smallexample come out as 8pt or so? It definitely looks smaller than
10pt on my screen.
Kind regards, Jon
[MIPS]question about floating point conditional branch
Hello, In mips.md, conditional branch insns are all set with the attribute value 'branch'. But floating point instructions such as bc1f will reserve falu unit instead of ialu. So there's a problem when you try to describe pipeline for 'branch' insns. Define the ialu as the reservation for all 'branch' insns? Is it OK? Eric Fisher 2008-11-3
Is there any plan for "data propagation from Tree SSA to RTL" to be in GCC mainline?
Hello, I found current modulo pipelining very inefficient for many loops. One reason is primitive cross-iteration memory dependency analysis. The add_inter_loop_mem_dep function in ddg.c just draws true dependency between every write and read pair. This is quite inadequate since many loops read from memory at the beginning of the loop and wrte to the memory at the end. In the end, we obtain schedule no better than list scheduling. I am aware of this work of propagating Tree-level dependency info to RTL (http://sysrun.haifa.il.ibm.com/hrl/greps2007/papers/melnik-propagation-greps2007.pdf). It should help a lot in improving memory dependency analysis. Is there any plan for this work to make into GCC mainline? Thanks in advance. Kind Regards, Bingfeng Mei Broadcom UK
Re: Patch for Re: out of date docs? (alpha/64bit vs. 32bit vs. cross)
Gerald Pfeifer writes: > >> In particular, I /assume/ it is false for any version that uses gmp. > > I believe that this is false these days. I believe that it has been > > false since a cross-compiler to the alpha required a 64-bit > > HOST_WIDE_INT, which was in gcc 3.4. > > Does this mean you (or Rainer) would approve the following documentation > update? ;-) at least I can't since I've never built cross-compilers to alpha-dec-osf, so I cannot say if it's true or not. Rainer - Rainer Orth, Faculty of Technology, Bielefeld University
GCC 4.3.3 Status Report (2008-11-03)
I'd like to apologize for sending this report so late. Status == The GCC 4.3 branch is open for regression and documentation fixes. The number of P1s grew a little bit, so the 4.3.3 release will need to be delayed by a few days until they are resolved or downgraded. Out of the 5 P1s, 2 were already fixed on the trunk and I'll just need to retest them in 4.3, one had a patch posted but no progress after patch review, one needs reghunt and analysis, one is currently assigned. Once all the P1s are resolved, 4.3.3 rc will be prepared. Quality Data Priority # Change from Last Report --- --- P15 + 3 P2 130 + 9 P33 - 1 --- --- Total 138 + 11 Previous Report === http://gcc.gnu.org/ml/gcc/2008-09/msg00379.html The next report for the 4.3 branch will be sent by Mark.
Re: About the "Build status for GCC 4.3" page
[removed gcc-patches from CC] On Sun, Nov 02, 2008 at 08:29:27PM +0100, Gerald Pfeifer wrote: > On Tue, 2 Sep 2008, Dennis Clarke wrote: > > Is there a way perhaps to update this page automagically? Maybe even > > a web based submission form with a a backend MySQL database ? I am > > thinking that we could drum up something to make the test results > > more readily available. > > I would be supportive of such an approach. Let's hear what Tom based > on his experience in the last months suggests. > Given the helperscripts I wrote to summarize the changes needed the most bothersome part of the current process is the manual editing of the buildstat.html file. It would probably be possible to script that part of the process too but I don't see how we can get around the need for a human to do quality control. It happens that results are duplicated, or posted twice and one of them is bad etc. it would be very difficult to pick that up automatically. Still if anyone wants to give it a shot I'm happy to contribute my current helperscripts if they can be of any help. -tgc
RE: [help-texinfo] Re: small font in gcc online docs
On Mon, 3 Nov 2008, Jonathan Grant wrote: > Perhaps GCC could use @example rather than @smallexample ? Consistent use of @smallexample comes from changes made for the printed manual published by GNU Press. GNU Press hasn't exactly been cooperative with the GCC community in merging their changes (dumping extensively modified sources instead of contributing individual logical patches and discussing them with the community as needed to get them merged), but the aim should still be to end up with one set of manual sources for all uses. -- Joseph S. Myers [EMAIL PROTECTED]
Re: using gcc's lexer/parser (was: Re: 'recording' program execution.)
"Edward Peschko" <[EMAIL PROTECTED]> writes: > wrt the below, I was giving it some thought, and was wondering how > usable the gcc lexer/parser combo was by itself, how 'pluggable' it > was - my hope was that I could take the lexer/parser and instead of > making an executable out of the incoming code, I could transform the > code in place, ie: add extra code of my own choosing that I would then > compile with gcc. > > How feasible would that be? Where's a good place to start? It's not really feasible. gcc's lexer and parser are not pluggable at all. Obviously it could be done, but it's quite a lot of work. Ian
RFC: A new meta intrinsic header file for x86 intrinsics
Hi, Icc will introduce to support intrinsics for current and future instruction sets, starting with AVX. We will submit a patch to implement , which will look like: --- #ifndef _IMMINTRIN_H_INCLUDED #define _IMMINTRIN_H_INCLUDED #ifdef __MMX__ #include #endif #ifdef __SSE__ #include #endif #ifdef __SSE2__ #include #endif #ifdef __SSE3__ #include #endif #ifdef __SSSE3__ #include #endif #if defined (__SSE4_2__) || defined (__SSE4_1__) #include #endif #if defined (__AES__) || defined (__PCLMUL__) #include #endif #ifdef __AVX__ AVX intrinsics #endif #endif /* _IMMINTRIN_H_INCLUDED */ --- My question is if we should put AVX intrinsics directly in immintrin.h or in a separate file. If we put AVX and future intrinsics directly in immintrin.h, immintrin.h may become very large and harder to maintain. Another choice is to put AVX intrinsics in a separate file, saying avxintrin.h: #ifndef _IMMINTRIN_H_INCLUDED # error "Never use directly; include instead." #else AVX intrinsics #endif /* _IMMINTRIN_H_INCLUDED */ Any comments? Thanks. -- H.J.
RE: [help-texinfo] Re: small font in gcc online docs
Does @smallexample come out as 8pt or so? It definitely looks smaller than 10pt on my screen. It comes out as whatever your browser tells it to, hopefully depending on what font size you have set. This is why different users see different things. The effect should be similar to using ..., although I expect there are browser(s) and version(s) which don't implement any of this properly in the first place. As for using @example instead of @smallexample, I suspect some of the examples would then become too wide for the printed manual. I'm sorry, but I just don't see anything to do here. Every option will displease someone. karl
Re: [help-texinfo] Re: small font in gcc online docs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Nov 03, 2008 at 01:00:31PM -, Jonathan Grant wrote: > Hello Karl, [...] > Perhaps GCC could use @example rather than @smallexample ? [lurker's opinion here, so take with appropriate amount of salt] I concur with Karl here. It's the combination of your browser and the stylesheet who decide how small a @smallexample ends up. It doesn't make much sense taking visibility at the abstract document level, since it's a property of the rendering medium and the user. You can easily set the minimum font size on your firefox, somewhere under edit->preferences->Content->Fonts->Advanced (or thereabouts -- don't you love GUI apps?). Regards - -- tomas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFJD+kmBcgs9XrR2kYRAngqAJ44Oe3FOU4nzFLFrptR20CwrH5ZWgCffLe1 DZ0MPqK4gSISZ+nJaS2K66U= =LqDG -END PGP SIGNATURE-
