[M3commit] CVS Update: cm3

[Rodney M. Bates]

Is there any documentation that tells what the invariants are on the
trees gdb can handle?  One would hope there would be.  Discovering
such by reading code in something as big as gcc is a very difficult
and error-prone job.  It sounds like you are having to discover them
by trial-and-error experiments, which is very much the hard way.

One would hope it exists, but then, from sad experiences, not necessarily
realistically expect so.

Jay Krell wrote:
> CVSROOT:	/usr/cvs
> Changes by:	jkrell at birch.	10/09/13 09:29:51
> 
> Modified files:
> 	cm3/m3-sys/m3cc/gcc/gcc/m3cg/: parse.c 
> 
> Log message:
> 	mark all non-bitfield fields as addressable
> 	This was part of a not yet very successful attempt at
> 	dealing with configure -enable-checking, and its flagging
> 	of our heavy use of bitfield refs.
> 	Hopefully we get something that isn't as bad as volatile.
> 	Hopefully we can remove this addressability actually,
> 	though I'll probably add more first (objects, arrays, etc.)
> 	
> 	Lots of cosmetic/cleanup.
> 	o => offset
> 	n => name
> 	len, n_len => name_length
> 	val => value
> 	p => proc
> 	l => label
> 	a, b, c, aren't terrible identifers, but l is particularly
> 	onerous due to resembles to 1
> 	t => type
> 	more to do here
> 	some functions have v and val, can't both be value
> 	tree *f => out_f, and use local f to avoid repeated derefs
> 	tree *v => out_v
> 	consolidate all tracing options
> 	There is just one variable now, option_trace_all, and
> 	all the options increment it. Almost all of the tracing
> 	is at level 1, a little is at 2.
> 	
> 	call one_gap/m3_gap unconditionally and have it do the check
> 	
> 	some missing spaces on function calls
> 	(really I'd just as soon remove them all, but they are
> 	fairly consistently present, so I'm following that style)
> 	
> 	remove the list of optimizations to possibly disable
> 	if need be, regain them from where they came
> 	
> 	tweak the options a little less; ongoing experimentation
> 	to reduce them, but some of them require a lot of
> 	debugging and fixing
> 	
> 	work in progress to synthesize field accesses on loads/stores
> 
>