Hi,
see my patch below for a fix of pr106845. I decided to allow bit_ranges
and byte_ranges to have a size of zero and rather only add an assertion
to the functions that assume a non-zero size. That way is more elegant in
the caller than restricting byte_range to only represent non-empty ranges.
On Sat, Sep 10, 2022 at 2:44 AM Takayuki 'January June' Suwa
wrote:
>
> This patch adds a new 3-instructions constant synthesis pattern:
>
> - A value that can fit into a signed 12-bit after a number of either bitwise
> left or right rotations:
> => "MOVI(.N) Ax, simm12" + "SSAI (1 ... 11) o
ping
> Hi,
>
> The IEEE_MODES_TYPE type and the two functions that get and set it were added
> in Fortran 2018. They can be implemented using the already existing
> target-specific functions. A future optimization could, on some targets,
> set/get all modes through one or two instructions o
Hi, Segher!
I'd like to thank you from the bottom of my heart !
I was happy to see my name listed in the github repository as well.
This will motivate me to do my best to commit more to GCC.. :)
Best Regards,
Takahashi Akari
https://github.com/takahashi-akari
GPG Key: 9DD8 F529 83A0 3182 D318 6
Hi!
Please cc: the rs6000 maintainers on rs6000 patches.
On Thu, Sep 08, 2022 at 08:20:07AM +0900, Akari Takahashi via Gcc-patches wrote:
> --- a/gcc/config/rs6000/rs6000.cc
> +++ b/gcc/config/rs6000/rs6000.cc
> @@ -18114,7 +18114,7 @@ get_memref_parts (rtx mem, rtx *base,
> HOST_WIDE_INT *offset
Hi Jakub, Rainer,
> On 9 Sep 2022, at 23:17, Jakub Jelinek wrote:
>
> On Fri, Sep 09, 2022 at 11:13:52PM +0100, Iain Sandoe wrote:
>> We already have such a header …
>> include/environ.h
>
> Ah, ok, then please just use it. Seems libgomp Makefile.am
> already includes -I$(top_srcdir)/../includ
ping
(with fix for the typo Bernhard noticed)
0001-Fortran-F2018-rounding-modes-changes.patch
Description: Binary data
> Le 31 août 2022 à 20:29, FX a écrit :
>
> This adds new F2018 features, that are not really enabled (because their
> runtime support is optional).
>
> 1. Add the new IEE
> Actuelly, that does not work. gfc_notify_std() should not be used at
> code-generation time, but in matching or setting-up symbols. It is never used
> in trans-* files, so I do not think I should introduce it now.
>
> Any hard objection to committing as it is? In the middle term, I intend to
This patch adds a new 3-instructions constant synthesis pattern:
- A value that can fit into a signed 12-bit after a number of either bitwise
left or right rotations:
=> "MOVI(.N) Ax, simm12" + "SSAI (1 ... 11) or (21 ... 31)"
+ "SRC Ax, Ax, Ax"
gcc/ChangeLog:
* config/xten