The 07/13/2022 12:55, David Malcolm wrote:
> On Wed, 2022-07-13 at 16:01 +0200, Florian Weimer wrote:
> > * David Malcolm:
> GCC trunk's -fanalyzer implements the new warnings via a state machine
> for file-descriptor values; it currently has rules for handling "open",
> "close", "read", and "write
Hi Sir/madam,
Greetings of the day.
We provide a leads database to increase Leads ratio along with closers ratio
and we served more than 2400+ clients globally.
We have "SCHOOLS DEALS DATABASE" for promoting and pitching your unique
services ?
Other lists we have : parents da
Hello,
I'm looking for some help in how to create a new function at compile time /
link time. The idea is an alternative form of constant propagation.
The current implementation of ipa-cp, may specialize functions for which
arguments may be known at compile time. Call graph edges from the caller
Hi Martin,
thanks a lot for your help! You were right! I am now able to call
make_edge_direct_to_target during WPA.
-Erick
On Thu, Jul 14, 2022 at 2:35 PM Erick Ochoa via Gcc wrote:
>
> Hello,
>
> I'm looking for some help in how to create a new function at compile time /
> link time. The idea is an alternative form of constant propagation.
>
> The current implementation of ipa-cp, may specialize functions for which
>
On Thu, Jul 14, 2022 at 3:27 PM Richard Biener
wrote:
>
> On Thu, Jul 14, 2022 at 2:35 PM Erick Ochoa via Gcc wrote:
> >
> > Hello,
> >
> > I'm looking for some help in how to create a new function at compile time /
> > link time. The idea is an alternative form of constant propagation.
> >
> > T
Hi Richard,
>
> > So instead of wrapping the function why not transform the original
> function
> > to have a prologue doing a runtime check for the compile-time specialized
> > versions and perform tail-calls to them?
> >
> > What I'm missing is who would call mul_test_param in your case?
>
The
On Thu, Jul 14, 2022 at 3:42 PM Erick Ochoa wrote:
>
> Hi Richard,
>
>
>> >
>> > So instead of wrapping the function why not transform the original function
>> > to have a prologue doing a runtime check for the compile-time specialized
>> > versions and perform tail-calls to them?
>> >
>> > What I
On Thu, 14 Jul 2022 at 15:51, Richard Biener
wrote:
> With a value-profile it would be per call site and IPA-CP can use that
> to direct the cloning. I'm not sure how many
> values a value histogram can track reliably here.
>
Last time I checked, value profiling can only track a single value pe
On 7/14/22 16:08, Erick Ochoa via Gcc wrote:
> Last time I checked, value profiling can only track a single value per
> statement.
Hi.
Take a look at HIST_TYPE_INDIR_CALL which we use for tracking at maximum 32
(#define GCOV_TOPN_MAXIMUM_TRACKED_VALUES 32) and we use for indirect call
speculative
On Thu, 14 Jul 2022 at 16:10, Martin Liška wrote:
> On 7/14/22 16:08, Erick Ochoa via Gcc wrote:
> > Last time I checked, value profiling can only track a single value per
> > statement.
>
> Hi.
>
> Take a look at HIST_TYPE_INDIR_CALL which we use for tracking at maximum 32
> (#define GCOV_TOPN_M
On Thu, 2022-07-14 at 09:30 +0100, Szabolcs Nagy wrote:
> The 07/13/2022 12:55, David Malcolm wrote:
> > On Wed, 2022-07-13 at 16:01 +0200, Florian Weimer wrote:
> > > * David Malcolm:
> > GCC trunk's -fanalyzer implements the new warnings via a state
> > machine
> > for file-descriptor values; it
On Thu, 2022-06-23 at 19:20 -0400, David Malcolm wrote:
> On Fri, 2022-06-24 at 00:00 +0530, Mir Immad wrote:
[...snip...]
> > +
> > +enum access_mode
> > +fd_state_machine::get_access_mode_from_flag (int flag) const
> > +{
> > + /* FIXME: this code assumes the access modes on the host and
> > +
We are delighted to announce the start of the public review period for psABI.
The review period begins today, 2022/07/14, and ends on 2022/08/29 (inclusive).
This Non-ISA specification is described in the PDF available at:
https://github.com/riscv-non-isa/riscv-elf-psabi-doc/releases/tag/v1.0-rc3
Hi,
As far as I understand the currently available plugin extension points, it is
not possible to modify template argument deduction algorithm (except the
theoretical possibility to completely override parsing step). However, such
opportunity might be beneficial for projects like libpqxx, for exam
On 7/14/22 08:22, David Malcolm via Libc-alpha wrote:
The analyzer now attempts to track both file descriptors and stdio
streams, so we probably need to special-case fdopen
You probably also need to special-case fileno, which goes the opposite
direction.
If you're handling DIR *, fdopendir a
Snapshot gcc-10-20220714 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/10-20220714/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 10 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Finally got some details about the icache snoop question so just coming
back to this now, sorry for the delay... (POWER10 does support the
coherent icache flush sequence as expected, there was some updates to
the UM wording but that will be fixed).
Excerpts from Segher Boessenkool's message of M
Excerpts from Segher Boessenkool's message of May 25, 2022 4:32 am:
> On Tue, May 24, 2022 at 11:52:00AM +0200, Florian Weimer wrote:
>> * Nicholas Piggin:
>>
>> > +2. Facilities
>> > +-
>> > +The Power ISA uses the term "facility" to describe a class of
>> > instructions,
>> > +regis
Take the arm64 HWCAP documentation file and adjust it for powerpc.
Signed-off-by: Nicholas Piggin
---
Thanks for the comments.
v2:
- Addition of "categories" paragraph.
- Change "features should not be probed via other means" to "HWCAP is
preferred".
- Speling fix.
-
Documentation/powerpc/el
20 matches
Mail list logo
