On 03/03/2024 09:47, Wols Lists wrote:
I'm getting this output from
emerge --update --newuse --deep --with-bdeps=y @world
whoops I mean "emerge --depclean"
I'm trying to get a clean system, and don't know what exactly is wrong,
or what to try ...
Cheers,
Wol
in the spdx. There is the
sourceInfo field that lists fixed CVEs, but I don't know how to encode this in
CycloneDX. How is this done with SDPX? Does anyone do CVE analysis with SPDX?
Regards Jörg
deptrack-spdx-upoad
Description: deptrack-spdx-upoad
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all
I'm getting this output from
emerge --update --newuse --deep --with-bdeps=y @world
Calculating dependencies... done!
* Dependencies could not be completely resolved due to
* the following required packages not being installed:
*
* >=dev-libs/icu-73.1:0/73.1= pulled in by:
*
On Fri, 2024-03-01 at 20:28 -0600, Doug Newgard wrote:
> > ..dependencies. Probably, most of the users already noticed that.
>
> See
> https://gitlab.archlinux.org/archlinux/packaging/packages/udisks2/-
> /issues/1
Very helpful - thanks
--
Gene
On Fri, 2024-03-01 at 23:04 +0100, Abraham S.A.H. wrote:
> Hello everyone,
>
> Probably a little late, but I noticed that `plugins of libblockdev`
...
FYI - Similar comment came up last week - this thread:
On 11/01/2024 14:35, Szabolcs Nagy wrote:
> The branch-protection types are target specific, not the same on arm
> and aarch64. This currently affects pac-ret+b-key, but there will be
> a new type on aarch64 that is not relevant for arm.
>
> After the move, change aarch_ identifiers to aarch64_
On 27/02/2024 13:56, Andre Vieira wrote:
>
> This patch adds support for MVE Tail-Predicated Low Overhead Loops by using
> the
> doloop funcitonality added to support predicated vectorized hardware loops.
>
> gcc/ChangeLog:
>
> * config/arm/arm-protos.h (arm_target_bb_ok_for_lob): Change
On 27/02/2024 13:56, Andre Vieira wrote:
>
> This patch adds support in the target agnostic doloop pass for the detection
> of
> predicated vectorized hardware loops. Arm is currently the only target that
> will make use of this feature.
>
> gcc/ChangeLog:
>
> * df-core.cc
On 27/02/2024 13:56, Andre Vieira wrote:
>
> This patch fixes the erroneous use of a mode attribute without a mode iterator
> in the pattern and removes unused unspecs and iterators.
>
> gcc/ChangeLog:
>
> * config/arm/iterators.md (supf): Remove VMLALDAVXQ_U, VMLALDAVXQ_P_U,
>
On 27/02/2024 13:56, Andre Vieira wrote:
>
> This patch annotates some MVE across lane instructions with a new attribute.
> We use this attribute to let the compiler know that these instructions can be
> safely implicitly predicated when tail predicating if their operands are
> guaranteed to have
On 27/02/2024 13:56, Andre Vieira wrote:
>
> This patch adds an attribute to the mve md patterns to be able to identify
> predicable MVE instructions and what their predicated and unpredicated
> variants
> are. This attribute is used to encode the icode of the unpredicated variant
> of
> an
On 19/02/2024 09:13, Torbjörn SVENSSON wrote:
> Ok for trunk and releases/gcc-13?
> Regtested on top of 945cb8490cb for arm-none-eabi, without any regression.
>
> Backporting to releases/gcc-13 will change -std=c23 to -std=c2x.
Jakub has just pushed a different fix for this, so I don't think we
On 01/03/2024 04:38, Alexandre Oliva wrote:
> Hello, Matthew,
>
> Thanks for the review.
For closure, Jakub has just pushed a patch to the generic code, so I don't
think we need this now.
R.
>
> On Feb 26, 2024, Matthew Malcomson wrote:
>
>> I think you're right that the AAPCS32 requires
On 13/01/2024 20:46, Thiago Jung Bauermann wrote:
> Since commit 2c3db94d9fd ("c: Turn int-conversion warnings into
> permerrors") the test fails with errors such as:
>
> FAIL: gcc.target/arm/acle/cde-mve-error-2.c -O0 (test for errors, line
> 32)
> FAIL:
On 01/03/2024 14:23, Andre Vieira (lists) wrote:
> Hi Thiago,
>
> Thanks for this, LGTM but I can't approve this, CC'ing Richard.
>
> Do have a nitpick, in the gcc/testsuite/ChangeLog: remove 'gcc/testsuite'
> from bullet points 2-4.
>
Yes, this is OK with the change
Hi Thiago,
Thanks for this, LGTM but I can't approve this, CC'ing Richard.
Do have a nitpick, in the gcc/testsuite/ChangeLog: remove
'gcc/testsuite' from bullet points 2-4.
Kind regards,
Andre
On 13/01/2024 00:55, Thiago Jung Bauermann wrote:
Since commits 2c3db94d9fd ("c: Turn
On 29/02/2024 15:55, Jakub Jelinek wrote:
> On Thu, Feb 29, 2024 at 02:14:05PM +, Richard Earnshaw wrote:
>>> I tried the above on arm, aarch64 and x86_64 and that seems fine,
>>> including the new testcase you added.
>>>
>>
>> I should mention though, that INIT_CUMULATIVE_ARGS on arm ignores
On 29/02/2024 17:56, Jakub Jelinek wrote:
> On Thu, Feb 29, 2024 at 05:51:03PM +, Richard Earnshaw (lists) wrote:
>> Oh, but wait! Perhaps that now falls into the initial 'if' clause and we
>> never reach the point where you pick zero. So perhaps I'm worrying about
>>
Hi,
Bootstrapped and tested the gcc-13 backport of this on gcc-12 for
aarch64-unknown-linux-gnu and x86_64-pc-linux-gnu and no regressions.
OK to push to gcc-12 branch?
Kind regards,
Andre Vieira
On 10/11/2023 13:16, Richard Biener wrote:
The following fixes the issue that when SLP stmts
On 29/02/2024 17:55, Andrew Pinski (QUIC) wrote:
>> -Original Message-
>> From: Maxim Kuvyrkov
>> Sent: Thursday, February 29, 2024 9:46 AM
>> To: Andrew Pinski (QUIC)
>> Cc: Evgeny Karpov ; Andrew Pinski
>> ; Richard Sandiford ; gcc-
>> patc...@gcc.gnu.org; 10wa...@gmail.com;
On 29/02/2024 17:38, Jakub Jelinek wrote:
> On Thu, Feb 29, 2024 at 05:23:25PM +, Richard Earnshaw (lists) wrote:
>> On 29/02/2024 15:55, Jakub Jelinek wrote:
>>> On Thu, Feb 29, 2024 at 02:14:05PM +, Richard Earnshaw wrote:
>>>>> I tried the above on arm,
On 29/02/2024 15:55, Jakub Jelinek wrote:
> On Thu, Feb 29, 2024 at 02:14:05PM +, Richard Earnshaw wrote:
>>> I tried the above on arm, aarch64 and x86_64 and that seems fine,
>>> including the new testcase you added.
>>>
>>
>> I should mention though, that INIT_CUMULATIVE_ARGS on arm ignores
On 27/02/2024 17:25, Jakub Jelinek wrote:
> On Tue, Feb 27, 2024 at 04:41:32PM +, Richard Earnshaw wrote:
>>> 2023-01-09 Jakub Jelinek
>>>
>>> PR target/107453
>>> * calls.cc (expand_call): For calls with
>>> TYPE_NO_NAMED_ARGS_STDARG_P (funtype) use zero for n_named_args.
>>>
On 29/02/2024 10:22, Christophe Lyon via Gcc wrote:
> Hi!
>
> Sorry for cross-posting, but I'm not sure the rules/guidelines are the
> same in gcc vs binutils/gdb.
>
> TL;DR: are there some guidelines about how to use/enable maintainer-mode?
>
> In the context of the Linaro CI, I've been
I can tell you there is significant spam from that Microsoft IP space. That
spamcop doesn't have false positives, but rather due to the sharing of IP
space, senders that aren't spammers get tarred with the same brush as the
spammers. I did a grep on the maillog files and that is a firehose of
On 27/02/2024 08:47, Richard Biener wrote:
On Mon, 26 Feb 2024, Andre Vieira (lists) wrote:
On 05/02/2024 09:56, Richard Biener wrote:
On Thu, 1 Feb 2024, Andre Vieira (lists) wrote:
On 01/02/2024 07:19, Richard Biener wrote:
On Wed, 31 Jan 2024, Andre Vieira (lists) wrote
From: Alexis Lothoré
The recently introduced postactions module can raise, on failing ptests,
the following warning:
WARNING: core-image-ptest-glib-2.0-1.0-r0 do_testimage: Can not get host
disk usage: [Errno 2] No such file or directory: '/usr/bin/df'
The issue is likely not happening
On 28/02/2024 02:17, Jack wrote:
On 2/27/24 20:54, Adam Carter wrote:
To clean up csv files I use excel's find/replace to swap the commas
occurring within fields for something benign. How does this magic
work? Different character sets within the same file?
Is it possible to do this with
My sender_access file contains
charity.donation.jp REJECT
postmap -q charity.donation.jp hash:sender_access
REJECT
So it returns REJECT as expected. However testing some random users at
the domain:
postmap -q m...@charity.donation.jp hash:sender_access
returns nothing. Is the domain being
Well do I put the domain in sender_access or sender_checks?
It looks like sender_access with an OK since it acts on the FROK field.
https://www.postfix.org/postconf.5.html
I have a sender_checks file but I don't see that on the postfix.org website. Is
that a deprecated parameter?
Feb 27, 2024
I still have that problem with the sender that used a spammy microsoft
server that gets rejected by IP for using spamcop. I put the domain in
the client_checks file but the sender gets bounced.
postconf mail_version
mail_version = 3.8.1
compatibility_level = 2
The client_checks line was
Hey,
Dropped the first patch and dealt with the comments above, hopefully I
didn't miss any this time.
--
This patch adds support for C23's _BitInt for the AArch64 port when
compiling
for little endianness. Big Endianness requires further target-agnostic
On 05/02/2024 09:56, Richard Biener wrote:
On Thu, 1 Feb 2024, Andre Vieira (lists) wrote:
On 01/02/2024 07:19, Richard Biener wrote:
On Wed, 31 Jan 2024, Andre Vieira (lists) wrote:
The patch didn't come with a testcase so it's really hard to tell
what goes wrong now and how
On 26/02/2024 16:05, Wilco Dijkstra wrote:
> Hi Richard,
>
>> Did you test this on a thumb1 target? It seems to me that the target parts
>> that you've
>> removed were likely related to that. In fact, I don't see why this test
>> would need to be changed at all.
>
> The testcase explicitly
On 23/02/2024 15:46, Wilco Dijkstra wrote:
> Hi Richard,
>
>> This bit isn't. The correct fix here is to fix the pattern(s) concerned to
>> add the missing predicate.
>>
>> Note that builtin-bswap.x explicitly mentions predicated mnemonics in the
>> comments.
>
> I fixed the patterns in v2.
Hello,
this small series is related to some disk space issue observed by the SWAT
team (see [1]) which eventually leads to tests failure. In order to help
diagnose those issues, I propose to enrich the retrieved artifacts with
some additional data, like disk usage on target and on host (in case
From: Alexis Lothoré
Since the target under test can be a virtualized guest, when some tests
fail because of disk usage (see [1]), also fetch disk usage statistics from
host to allow checking whether a host disk space saturation could affect
running tests.
[1]
From: Alexis Lothoré
Multiple places in oeqa need to get the log output path, and redefine a
small helper to accomplish this
Define this helper in lib/oeqa/utils/__init__.py and import it wherever
needed to allow using it.
Signed-off-by: Alexis Lothoré
---
There is one additional place
From: Alexis Lothoré
In order to debug issues related to disk space (see [1]), add a failed
tests post action to retrieve disk usage on the target. Rely on the test
context object to run the corresponding command onto the target
[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=15220
From: Alexis Lothoré
In order to be able to create actions that could store new files during
failed test post actions, we need to split artifacts directory creation
from artifacts retrieval.
Create a new dedicated action to create artifacts main directory so we can
add actions creating files in
From: Alexis Lothoré
testimage is able to detect whenever a test run leads to some tests
failing, and execute some actions in this case. The only action currently
defined in such case is to retrieve artifacts from the target under test,
as listed in TESTIMAGE_FAILED_QA_ARTIFACTS
In order to be
On Sun, 2024-02-25 at 12:07 +0100, SET wrote:
>
>
>
This looks like the same bug and should be fixed with 1.46.0-2 now in
testing [1]
[1]
https://gitlab.archlinux.org/archlinux/packaging/packages/networkmanager/-/issues/2
--
Gene
On Sun, 2024-02-25 at 08:38 +0100, SET wrote:
> Hi,
>
> Since yesterday's upgrade, it's not possible to establish IPV4
> networking with
>
If your network manager backend is still wpa-supplicant it may be worth
trying iwd.
i.e.
Edit /etc/NetworkManager/conf.d/wifi_backend.conf :
[device]
Hi all,
The Wikidata-Toolkit Java library has been doing that for a while, but I
think there has been some changes in the RDF format that have not been
reflected in Wikidata-Toolkit yet.
https://github.com/Wikidata/Wikidata-Toolkit/
There is an example Java application taking a JSON dump
That should work. Thanks
https://www.postfix.org/access.5.html
Feb 24, 2024 8:05:00 AM Matus UHLAR - fantomas via Postfix-users
:
>>> On 24.02.24 00:49, lists--- via Postfix-users wrote:
>>>> I have set up rbl_override for the sender's domain.
> [...]
>>&
https://www.dnswl.org/?page_id=15
I get your point but this is for a different blocking list. That is spamcop and
spamassassin have different blocking lists.
What I really need is a way to make the rbl_override work for the domain name
that has been related.
I am going to review my logs
6:03:54 AM Matus UHLAR - fantomas via Postfix-users
:
> On 24.02.24 00:49, lists--- via Postfix-users wrote:
>> I have set up rbl_override for the sender's domain. However it
>> occasionally gets blocked by spamcop. The user owns a domain but relays
>> the mail from outlook.
&g
On Fri, 2024-02-23 at 22:13 -0600, David C. Rankin wrote:
> All, David,
>
> ...
> The trend I've seen over the past several years is to subdivide
> packages,
> which as long as they continue to work is fine, but at some point it
> does
...
Its an interesting question how best to offer a
I have set up rbl_override for the sender's domain. However it
occasionally gets blocked by spamcop. The user owns a domain but relays
the mail from outlook.
Here is the bounce message the user received:
**
Remote server returned '550 5.7.514 Decision Engine classified the mail
item
On 2/23/24 18:27, Richard Purdie wrote:
> On Fri, 2024-02-23 at 16:16 +0100, Alexis Lothoré via
> lists.openembedded.org wrote:
>> From: Alexis Lothoré
>>
>> Multiple places in oeqa need to get the log output path, and redefine
>> a
>> small helper to accomplish this
>>
>> Define this helper in
On 23/02/2024 00:28, Grant Edwards wrote:
In my experience, 's bootloader does not boot other
installations by calling other bootloaders. It does so by rummaging
through all of the other partitions looking for kernel images, intird
files, grub.cfg files, etc. It then adds menu entries to the
Hello,
this small series is related to some disk space issue observed by the SWAT
team (see [1]) which eventually leads to tests failure. In order to help
diagnose those issues, I propose to enrich the retrieved artifacts with
some additional data, like disk usage on target and on host (in case
From: Alexis Lothoré
In order to be able to create actions that could store new files during
failed test post actions, we need to split artifacts directory creation
from artifacts retrieval.
Create a new dedicated action to create artifacts main directory so we can
add actions creating files in
From: Alexis Lothoré
In order to debug issues related to disk space (see [1]), add a failed
tests post action to retrieve disk usage on the target. Rely on the test
context object to run the corresponding command onto the target
[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=15220
From: Alexis Lothoré
Since the target under test can be a virtualized guest, when some tests
fail because of disk usage (see [1]), also fetch disk usage statistics from
host to allow checking whether a host disk space saturation could affect
running tests.
[1]
From: Alexis Lothoré
testimage is able to detect whenever a test run leads to some tests
failing, and execute some actions in this case. The only action currently
defined in such case is to retrieve artifacts from the target under test,
as listed in TESTIMAGE_FAILED_QA_ARTIFACTS
In order to be
From: Alexis Lothoré
Multiple places in oeqa need to get the log output path, and redefine a
small helper to accomplish this
Define this helper in lib/oeqa/utils/__init__.py and import it wherever
needed to allow using it.
Signed-off-by: Alexis Lothoré
---
There is one additional place
On 2/23/24 15:42, Richard Purdie wrote:
> On Fri, 2024-02-23 at 15:03 +0100, Alexis Lothoré via lists.openembedded.org
> wrote:
>> From: Alexis Lothoré
>>
>> testimage is able to detect whenever a test run leads to some tests
>> failing, and execute some actions in this case. The only action
Hello,
this small series is related to some disk space issue observed by the SWAT
team (see [1]) which eventually leads to tests failure. In order to help
diagnose those issues, I propose to enrich the retrieved artifacts with
some additional data, like disk usage on target and on host (in case
From: Alexis Lothoré
Since the target under test can be a virtualized guest, when some tests
fail because of disk usage (see [1]), also fetch disk usage statistics from
host to allow checking whether a host disk space saturation could affect
running tests.
[1]
From: Alexis Lothoré
In order to debug issues related to disk space (see [1]), add a failed
tests post action to retrieve disk usage on the target. Rely on the test
context object to run the corresponding command onto the target
[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=15220
From: Alexis Lothoré
testimage is able to detect whenever a test run leads to some tests
failing, and execute some actions in this case. The only action currently
defined in such case is to retrieve artifacts from the target under test,
as listed in TESTIMAGE_FAILED_QA_ARTIFACTS
In order to be
From: Alexis Lothoré
In order to be able to create actions that could store new files during
failed test post actions, we need to split artifacts directory creation
from artifacts retrieval.
Create a new dedicated action to create artifacts main directory so we can
add actions creating files in
From: Alexis Lothoré
Multiple places in oeqa need to get the log output path, and redefine a
small helper to accomplish this
Define this helper in lib/oeqa/utils/__init__.py and import it wherever
needed to allow using it.
Signed-off-by: Alexis Lothoré
---
There is one additional place
On 21/02/2024 17:47, Evgeny Karpov wrote:
> Hello,
>
> We would like to take your attention to the review of changes for the
> new GCC target, aarch64-w64-mingw32. The new target will be
> supported, tested, added to CI, and maintained by Linaro. This marks
> the first of three planned patch
On 21/02/2024 18:40, Evgeny Karpov wrote:
>
+aarch64-*-mingw*)
This doesn't match the glob pattern you added to config.gcc in an earlier
patch, but see my comment on that. The two should really be consistent with
each other or you might get build failures late on.
R.
On 21/02/2024 18:38, Evgeny Karpov wrote:
>
For this change you might want to put some form of re-direct in the manual
under the old name so that anybody used to looking for the old entry will know
where things have been moved to. Something like
x86 Windows Options
See xref(Cygwin and MinGW
On 21/02/2024 18:36, Evgeny Karpov wrote:
>
+/* GNU as supports weak symbols on PECOFF. */
+#ifdef HAVE_GAS_WEAK
Can't we assume this is true? It was most likely needed on i386 because
support goes back longer than the assembler had this feature, but it looks like
it was added in 2000, or
On 21/02/2024 18:30, Evgeny Karpov wrote:
>
+ tm_defines="${tm_defines} TARGET_ARM64_MS_ABI=1"
I missed this on first reading...
The GCC port name uses AARCH64, please use that internally rather than other
names. The only time when we should be using ARM64 is when it's needed for
On 21/02/2024 18:30, Evgeny Karpov wrote:
>
+/* X18 reserved for the TEB on Windows. */
+#ifdef TARGET_ARM64_MS_ABI
+# define FIXED_X18 1
+# define CALL_USED_X18 0
+#else
+# define FIXED_X18 0
+# define CALL_USED_X18 1
+#endif
I'm not overly keen on ifdefs like this (and the one below), it can
On 21/02/2024 18:26, Evgeny Karpov wrote:
>
+/* Available call ABIs. */
+enum calling_abi
+{
+ AARCH64_EABI = 0,
+ MS_ABI = 1
+};
+
The convention in this file seems to be that all enum types to start with
aarch64. Also, the enumeration values should start with the name of the
enumeration
On 21/02/2024 18:16, Evgeny Karpov wrote:
>
+aarch64*-*-mingw*)
Other targets are a bit inconsistent here as well, but, as Andrew mentioned, if
you don't want to handle big-endian, it might be better to match
aarch64-*-mingw* here.
R.
On 21/02/2024 21:34, rep.dot@gmail.com wrote:
> On 21 February 2024 19:34:43 CET, Evgeny Karpov
> wrote:
>>
>
> Please use git send-email. Your mail ends up as empty as here, otherwise.
I don't see anything wrong with it; niether does patchwork
On 21/02/2024 14:34, Wilco Dijkstra wrote:
>
> By default most patterns can be conditionalized on Arm targets. However
> Thumb-2 predication requires the "predicable" attribute be explicitly
> set to "yes". Most patterns are shared between Arm and Thumb(-2) and are
> marked with "predicable".
On 2/21/24 08:56, Richard Purdie wrote:
> On Wed, 2024-02-21 at 08:53 +0100, Alexis Lothoré wrote:
>> On 2/21/24 08:34, Richard Purdie wrote:
>>> On Tue, 2024-02-20 at 21:01 +0100, Alexis Lothoré via
>>> lists.openembedded.org wrote:
From: Alexis Lothoré
>>
>> [...]
>>
Hello Richard,
On 2/21/24 08:34, Richard Purdie wrote:
> On Tue, 2024-02-20 at 21:01 +0100, Alexis Lothoré via
> lists.openembedded.org wrote:
>> From: Alexis Lothoré
[...]
>> +##
>> +# General post actions runner
>>
From: Alexis Lothoré
In order to debug issues related to disk space (see [1]), add a failed
tests post action to retrieve disk usage on the target. Rely on the test
context object to run the corresponding command onto the target
[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=15220
From: Alexis Lothoré
Since the target under test can be a virtualized guest, when some tests
fail because of disk usage (see [1]), also fetch disk usage statistics from
host to allow checking whether a host disk space saturation could affect
running tests.
[1]
Hello,
this small series is related to some disk space issue observed by the SWAT
team (see [1]) which eventually leads to tests failure. In order to help
diagnose those issues, I propose to enrich the retrieved artifacts with
some additional data, like disk usage on target and on host (in case
From: Alexis Lothoré
In order to be able to create actions that could store new files during
failed test post actions, we need to split artifacts directory creation
from artifacts retrieval.
Create a new dedicated action to create artifacts main directory so we can
add actions creating files in
From: Alexis Lothoré
testimage is able to detect whenever a test run leads to some tests
failing, and execute some actions in this case. The only action currently
defined in such case is to retrieve artifacts from the target under test,
as listed in TESTIMAGE_FAILED_QA_ARTIFACTS
In order to be
Chain mount. Chuck has them as does PV and CommScope.Regards,Jeff Jeff BroadwickCTIconnect312-205-2519 Office574-220-7826 Celljbroadw...@cticonnect.comOn Feb 20, 2024, at 1:06 PM, Ken Hohhof wrote:I think I’ve got some of the Valmont ones on the shelf. Like everything from SitePro1, they are
On Sonntag, 18. Februar 2024 01:42:30 CET Keifer Bly wrote:
Every few months the same question with the same log messages :-(
> 00:36:35.000 [warn] You are running Tor as root. You don't need to, and you
> probably shouldn't.
^^Still not fixed.
> Feb 18 00:36:34.640 [notice] Opening OR listener
From: Alexis Lothoré
Despite managing to retrieve the failed ptests artifacts, testimage seems
to dump some retrieval errors like the following one:
WARNING: core-image-ptest-valgrind-1.0-r0 do_testimage: Can not retrieve
/usr/lib/valgrind/ptest from test target
Log the corresponding exception
Fixes [YOCTO #15120]
Consider OVERLAYFS_WRITABLE_PATHS as dependecy of do_create_overlayfs_units() in
order to rebuild the recipe when changing the used mount point.
Tested in a local recipe by changing the used mount point and verified that the
recipe was re-build: passed
Signed-off-by:
On 19/02/2024 16:17, Jakub Jelinek wrote:
On Mon, Feb 19, 2024 at 04:13:29PM +, Andre Vieira (lists) wrote:
Replaced uses of __seg_gs with the MACRO SEG defined in the testcase to pick
(if any) the right __seg_{gs,fs} keyword based on target.
gcc/testsuite/ChangeLog:
* gcc.dg
Replaced uses of __seg_gs with the MACRO SEG defined in the testcase to
pick (if any) the right __seg_{gs,fs} keyword based on target.
gcc/testsuite/ChangeLog:
* gcc.dg/bitint-86.c (__seg_gs): Replace with SEG MACRO.diff --git a/gcc/testsuite/gcc.dg/bitint-86.c
Regards,
Andre
On 20/12/2023 14:30, Richard Biener wrote:
On Wed, 20 Dec 2023, Andre Vieira (lists) wrote:
Thanks, fully agree with all comments.
gcc/ChangeLog:
PR target/112787
* tree-vect-generic (type_for_widest_vector_mode): Change function
to use original vector
On 19/02/2024 10:58, Tamar Christina wrote:
>> -Original Message-
>> From: Tamar Christina
>> Sent: Thursday, February 15, 2024 11:05 AM
>> To: Richard Earnshaw (lists) ; gcc-
>> patc...@gcc.gnu.org
>> Cc: nd ; Marcus Shawcroft ; Kyrylo
>> Tkac
Hey Cotty,
> On 18 Feb 2024, at 23:43, Steve Cottrell wrote:
>
> Hi Pentaxers
>
> I know some of you shoot video now and then, perhaps even do a little editing.
>
> I’ve put together this *little* (ahem) film about the post-production process
> for newbies that some might find interesting.
On Donnerstag, 15. Februar 2024 13:54:51 CET s7r wrote:
> I have recently found something interesting on my relays. On all relays
> and clients actually.
>
> As always I am using Debian and apt to get Tor from deb.torproject.org
> tor-nightly-main-bullseye main (for example). I also have the
On 12/02/2024 13:48, Matthieu Longo wrote:
> This patch marks a rev16 test as XFAIL for architectures having only Thumb1
> support. The generated code is functionally correct, but the optimization is
> disabled when -mthumb is equivalent to Thumb1. Fixing the root issue would
> requires changes
On 15/02/2024 10:57, Tamar Christina wrote:
> Hi All,
>
> This test has never worked on AArch64 since the day it was committed. It has
> a number of issues that prevent it from working on AArch64:
>
> 1. IEEE does not require that FP operations raise a SIGFPE for FP operations,
> only that
On 14/02/2024 09:20, Tejas Belagod wrote:
> On 2/7/24 11:41 PM, Richard Earnshaw (lists) wrote:
>> On 07/02/2024 07:59, Tejas Belagod wrote:
>>> This patch fixes a bug that causes indirect calls in PAC-enabled functions
>>> to be tailcalled incorrectly when all argume
On 09/02/2024 12:57, J. Roeleveld wrote:
I don't understand it exactly, but what I think happens is when I create
the snapshot it allocates, let's say, 1GB. As I write to the master
copy, it fills up that 1GB with CoW blocks, and the original blocks are
handed over to the backup snapshot. And
On 30/01/2024 17:07, Saurabh Jha wrote:
> Hey,
>
> Previously, this test was added to fix this bug:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112337. However, it did not
> check the compilation options before using them, leading to errors.
>
> This patch fixes the test by first checking
On 08/02/2024 06:38, J. Roeleveld wrote:
ZFS doesn't have this "max amount of changes", but will happily fill up the
entire pool keeping all versions available.
But it was easier to add zpool monitoring for this on ZFS then it was to add
snapshot monitoring to LVM.
I wonder, how do you deal
On 08/02/2024 06:32, J. Roeleveld wrote:
Personally, I'd go the MPL2 route, but that's my choice. It might not
suit you. But to achieve what you want, you need a copyleft, GPL-style
licence.
I'll have a look at that one.
Basically, each individual source file is copyleft, but not the work
On 07/02/2024 11:11, J. Roeleveld wrote:
On Tuesday, February 6, 2024 9:27:35 PM CET Wols Lists wrote:
On 06/02/2024 13:12, J. Roeleveld wrote:
Clearly Oracle likes this state of affairs. Either that, or they are
encumbered in some way from just GPLing the ZFS code. Since they on
paper own
On 07/02/2024 11:07, J. Roeleveld wrote:
Because snapshotting uses so much less space?
So much so that, for normal usage, I probably have no need to delete any
snapshots, for YEARS?
My comment was based on using rsync to copy from the source to the backup
filesystem.
Well, that's EXACTLY
101 - 200 of 37041 matches
Mail list logo
