Re: [Tux3] Tux3 report: Tux3 Git tree available

[Sam Ravnborg]

> 
> > > > - What's "L"?
> > > > 
> > > > 		printf("%Lx-", (L)begin);
> > > 
> > > A very handy way of working around 32/64 bit format string issues.  We
> > > just cast all the messy cases to (long long), aka (L).  All other
> > > solutions to this messy problem are worse in my opinion, but whatever
> > > the ruling is, is what we will do.  This is used heavily in tracing and
> > > dumping code, which can all be turned off with ifdefs, so it doesn't
> > > affect production kernel text.
> > 
> > What format string issues are we talking about here?
> > 
> > See, a number of them will be fixed real soon now (geologically
> > speaking) when various 64-bit architectures switch their s64/u64
> > implementation from `long' to `long long'.
> 
> Ah, that would be helpful.  But not done yet?  How long until it
> happens, and does it make sense to wait, so we can reduce the number
> of problems cases?  And... will it be all 64 bit arches or just some?
> Because this issue isn't solved if it isn't fixed for all arches.

Most if not all will hit mainline during coming merge window.
When an arch changes u64 becomes unsigned long long.

It is considered a 'must have' for 64 bit archs these days so
do not workaround it.

	Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/