Patch 3/3 is the update for the Local Register Variables page (attached).
This patch starts with a question. Looking at bug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64951 (register variable
with template function) is this a bug that will be fixed? Or a
limitation that should be doc'ed? B
Patch 2/3 is the update for the Global Register Variables page (attached).
Reviewing this patch is going to be difficult.
It's a lot easier to review a patch that just has a few lines of text
being added. However, this leads to 'chunky' docs with a bunch of
disjointed paragraphs (which is wha
On Mon, 12 Oct 2015, Jeff Law wrote:
> In the interest of keeping my sanity, I'd just change that last default value
> to something like "unknown type error" or somesuch. But I'm sure there's a
> better way. Suggestions?
The *right* fix is both of the following (either would suffice on its own
Having updated the docs for Basic asm, Extended asm, and Asm Labels, I
am now sending my patches for the last of the inline asm sections:
Explicit Reg Vars.
My first attempt to update this got postponed (see
https://gcc.gnu.org/ml/gcc-patches/2014-06/msg02369.html). This patch
addresses the
The avr-rtems port will not build using a trunk compiler on a system
with a reasonably modern glibc.
If we look at newlib-stdint.h, we have these wonderfully convoluted
conditionals like:
#define INT8_TYPE (CHAR_TYPE_SIZE == 8 ? "signed char" : 0)
They get more complex, but essentially they
> I can confirm that gnat-4.9 works OK (as well as gnat-4.6).
Great.
> I wonder whether bugzilla is still the right place to document this, given
> 4.8 is now end-of-lifed...do you know of anywhere appropriate?
This would be here I guess:
https://gcc.gnu.org/install/specific.html#arm-x-eabi
-
On 12/10/15 10:58, Eric Botcazou wrote:
Yes, that fixes the dependency problem; the build waits for the xsinfo to
terminate. This at least makes it easy to Ctrl-C and try again. Are we aware
of any reason why *not* to make that change?
You may have noticed that I had made it before you posted t
On Mon, Oct 12, 2015 at 1:06 PM, Abhishek Aggarwal
wrote:
> @Jonathan: The reason I started this discussion is due to my suspicion
> of a potential bug in gcc-4.9.2. However, I may be wrong. Here is the
> explanation:
I think everything is alright. The code is only emitted for the main
function,
@Stefan: Thanks a lot for replying. These are the excerpts from
http://www.uclibc.org/docs/psABI-i386.pdf (Section 2.2.2. Page 10):
"The end of the input argument area shall be aligned on a 16 (32, if
__m256 is passed on stack) byte boundary. In other words, the value
(%esp + 4) is always a multipl
On Sun, Oct 11, 2015 at 10:18 PM, Mikhail Maltsev wrote:
> Hi!
>
> SUSE performs periodic testing of GCC and publishes the results on their site:
> http://gcc.opensuse.org/ (many thanks for this great job!).
>
> I'm trying to perform some analysis of these results and asking for help with
> unders
Hi Guys,
I am applying the attached patch to add support for more MSP430 MCUs
to the MSP430 target. The names and data have been copied directly
from the the latest devices.csv file released by TI.
The patch also updates the documentation on the MSP430's -mmcu option
to note that if th
On 12 October 2015 at 10:11, Abhishek Aggarwal wrote:
> I was befuddled by the following 3 assembly instructions (generated
> right in the beginning of 'main' function):
>lea 0x4(%esp), %ecx
>and 0xfff0, %esp
>pushl -0x4(%ecx)
>
> I am not able to understand the purpose
> Yes, that fixes the dependency problem; the build waits for the xsinfo to
> terminate. This at least makes it easy to Ctrl-C and try again. Are we aware
> of any reason why *not* to make that change?
You may have noticed that I had made it before you posted this message. :-)
> The hang in xsinf
On Mon, Oct 12, 2015 at 11:11 AM, Abhishek Aggarwal
wrote:
> I was befuddled by the following 3 assembly instructions (generated
> right in the beginning of 'main' function):
>lea 0x4(%esp), %ecx
>and 0xfff0, %esp
>pushl -0x4(%ecx)
>
> I am not able to understand the p
Hi all
I was trying to compile the following code with gcc 4.9.2 on Ubuntu
14.04 x86_64 platform:
/* File a.cpp */
#include
int main (int argc, const char *argv[])
{
printf("Hello World!\n");
return 0;
}
Compilation commands are:
g++-4.9.2 -std=c++11 -g -O0 -fno-builtin -m32 a.cpp
I was t
15 matches
Mail list logo
