I installed this patch from David with an update to use the "Registers
are a scarce resource ..." text.
2 down, 1 to go. Thanks.
dw
On 10/21/2015 05:27 AM, Segher Boessenkool wrote:
On Tue, Oct 20, 2015 at 09:24:48PM -0700, David Wohlferd wrote:
+Registers can be a limited resource on some systems and allowing the
They are a limited resource on almost all systems. "Scarce resource"?
"Scarce" it is. I've left the rest al
On Tue, Oct 20, 2015 at 09:24:48PM -0700, David Wohlferd wrote:
> >>+Registers can be a limited resource on some systems and allowing the
> >They are a limited resource on almost all systems. "Scarce resource"?
>
> "Scarce" it is. I've left the rest alone for the moment, but how would
> you fee
On 10/20/2015 10:16 PM, David Wohlferd wrote:
- Eventually the compiler may work differently than it does now.
That is helpful. It's a way signaling that things may change and that
depending on the precise syntax and semantics may be unwise.
From time to time, particularly with GCC extension
Line too long. I know quite a bit of doc does that, but that's no
excuse :-)
Reduced to < 79.
+Registers can be a limited resource on some systems and allowing the
They are a limited resource on almost all systems. "Scarce resource"?
"Scarce" it is. I've left the rest alone for the mome
- Eventually the compiler may work differently than it does now.
That is helpful. It's a way signaling that things may change and that
depending on the precise syntax and semantics may be unwise.
From time to time, particularly with GCC extensions, it has been
necessary to declare certain u
On 10/20/2015 03:12 AM, Segher Boessenkool wrote:
On Mon, Oct 19, 2015 at 11:14:30PM -0600, Jeff Law wrote:
+All global register variable declarations must precede all function
+definitions. If such a declaration appears after function definitions,
+the declaration would be too late to prevent
On Mon, Oct 19, 2015 at 11:14:30PM -0600, Jeff Law wrote:
> >>+All global register variable declarations must precede all function
> >>+definitions. If such a declaration appears after function definitions,
> >>+the declaration would be too late to prevent the register from being used
> >>+for oth
On 10/19/2015 03:42 PM, Segher Boessenkool wrote:
+After defining a global register variable, for the duration of
+the current compilation:
It's probably better to say "for the current compilation unit"? There now
is LTO and whatnot.
Which raises the question, what happens for LTO? Do we stre
On 10/12/2015 05:07 PM, David Wohlferd wrote:
- There are unsourced, unsubstantiated reports that on some platforms,
certain things might or might not work.
Back when this was written (circa 1996), this would have been considered
helpful information -- having a system routine clobber a register
On Mon, Oct 12, 2015 at 04:07:48PM -0700, David Wohlferd wrote:
> Index: extend.texi
> ===
> --- extend.texi (revision 228690)
> +++ extend.texi (working copy)
> @@ -8506,7 +8506,8 @@
> @cindex global register variables
>
11 matches
Mail list logo
