gcc/gcc-TEST
gcc/gcc-TEST
15
Fork 27
forked from gcc/gcc-mirror
Code Issues Pull requests 33 Wiki Activity Actions

libgccjit: Handle missing types in jit_langhook_type_for_mode #87

Open
antoyo wants to merge 1 commit from antoyo/gcc:missing-types into trunk
pull from: antoyo/gcc:missing-types
merge into: gcc:trunk
Conversation 12 Commits 1 Files changed 1 +4
antoyo commented 2025-09-29 18:27:15 +00:00
Member
Copy link
gcc/jit/ChangeLog:

	* dummy-frontend.cc: Handle new types in jit_langhook_type_for_mode.

On some targets (I found this was the case for Aarch64, probably), we need to handle some float types in jit_langhook_type_for_mode.

CC: David Malcolm dmalcolm@redhat.com, jit@gcc.gnu.org

``` gcc/jit/ChangeLog: * dummy-frontend.cc: Handle new types in jit_langhook_type_for_mode. ``` On some targets (I found this was the case for Aarch64, probably), we need to handle some float types in jit_langhook_type_for_mode. CC: David Malcolm <dmalcolm@redhat.com>, <jit@gcc.gnu.org>
gcc/jit/ChangeLog:

	* dummy-frontend.cc: Handle new types in jit_langhook_type_for_mode.
forge-bot commented 2025-09-29 18:27:34 +00:00
Member
Copy link

Welcome to Sourceware Forge

Hi @antoyo, and thanks for your PR. This bot helps you send your patch series to the mailing list.

Please follow these guidelines to ensure a smooth submission.

Writing a Good PR Description

  • If your PR has multiple commits, write a meaningful description. It becomes the cover letter.
  • For a single commit, you can leave the description empty if the commit message is clear.

To CC reviewers, add at the end of your PR description one or more lines like this:

CC: Revi Ewer <revi.ewer@example.com>, Ill Takalook <ill.takalook@example.net>

Avoid copy-pasting a CC list from a previous PR. Doing so may cause failure to send the emails properly.

We recommend reviewing your commit messages carefully before submitting.

This project expects a specific format.
See Submitting Patches for details

Submitting Your Patch

To submit, you must be authorized. Ask any permitted contributor to authorize you by commenting: /allow. This is anyone who has been /allowed before.

Once allowed, comment: /submit

Use /preview to see the emails before sending. (Requires a public forge email.)

Responding to Reviews

Watch for replies on the mailing list. If not subscribed, you can reply by:

  1. Visiting inbox.sourceware.org
  2. Clicking (raw) on the email
  3. Importing it into your mail client

For Gmail:

curl -g --user "<Email>:<Password>" \
  --url "imaps://imap.gmail.com/INBOX" -T /path/to/raw.txt

Updating Your PR

  1. Push new commits, rebase and force push changes to the same branch as needed
  2. Update the PR description with a “Changes since vX” section
  3. Comment again with: /submit

Need help?

Consider joining the gcc and gcc-patches mailing lists..
For real time communication, check the gcc irc channels.

Or join #overseers on Libera Chat, particularly if this automation is not working (stay online to get replies, IRC does not save messages if people are not online).

<!-- pr-welcome --> # Welcome to Sourceware Forge Hi @antoyo, and thanks for your PR. This bot helps you send your patch series to the mailing list. Please follow these guidelines to ensure a smooth submission. ## Writing a Good PR Description - If your PR has **multiple commits**, write a meaningful description. It becomes the cover letter. - For **a single commit**, you can leave the description empty if the commit message is clear. To CC reviewers, add at the end of your PR description one or more lines like this: ```text CC: Revi Ewer <revi.ewer@example.com>, Ill Takalook <ill.takalook@example.net> ``` Avoid copy-pasting a CC list from a previous PR. Doing so may cause failure to send the emails properly. We recommend reviewing your commit messages carefully before submitting. This project expects a specific format. See [Submitting Patches](https://gcc.gnu.org/contribute.html#patches) for details ## Submitting Your Patch To submit, you must be authorized. Ask any permitted contributor to authorize you by commenting: `/allow`. This is anyone who has been `/allow`ed before. Once allowed, comment: `/submit` Use `/preview` to see the emails before sending. (Requires a public forge email.) ## Responding to Reviews Watch for replies on the mailing list. If not subscribed, you can reply by: 1. Visiting [inbox.sourceware.org](https://inbox.sourceware.org) 2. Clicking `(raw)` on the email 3. Importing it into your mail client For Gmail: ```sh curl -g --user "<Email>:<Password>" \ --url "imaps://imap.gmail.com/INBOX" -T /path/to/raw.txt ``` ## Updating Your PR 1. Push new commits, rebase and force push changes to the same branch as needed 2. Update the PR description with a “Changes since vX” section 3. Comment again with: `/submit` ## Need help? Consider joining the [gcc and gcc-patches mailing lists.](https://gcc.gnu.org/lists.html). For real time communication, check the [gcc irc channels](https://gcc.gnu.org/wiki/GCConIRC). Or join [`#overseers`](https://web.libera.chat/#overseers) on Libera Chat, particularly if this automation is not working (stay online to get replies, IRC does not save messages if people are not online).
antoyo commented 2025-09-29 18:29:50 +00:00
Author
Member
Copy link

I'm not sure how I could test this since this is not needed on x86-64. Any ideas?

I'm not sure how I could test this since this is not needed on x86-64. Any ideas?
antoyo commented 2025-09-29 18:30:02 +00:00
Author
Member
Copy link

/submit

/submit
forge-bot commented 2025-09-29 18:30:49 +00:00
Member
Copy link

Version 1 of this pull request has been stored. It includes the following commits:

  • libgccjit: Handle missing types in jit_langhook_type_for_mode - a8c7593204
<!-- pr-new-version --> Version 1 of this pull request has been stored. It includes the following commits: - libgccjit: Handle missing types in jit_langhook_type_for_mode - a8c7593204948a3ee3642c6d3dacb10bfe9df498
forge-bot commented 2025-09-29 18:30:50 +00:00
Member
Copy link

Pull Request versions:

# Base Head
1 850c1ad7e3 a8c7593204 (diff)

In order to compare , clone this repository and run

PR=87
git fetch origin "refs/versioned_pull/${PR}/*:refs/versioned_pull/${PR}/*"
PRV1=1
PRV2=2
git range-diff "refs/versioned_pull/${PR}/${PRV1}/base..refs/versioned_pull/${PR}/${PRV1}/head"  "refs/versioned_pull/${PR}/${PRV2}/base..refs/versioned_pull/${PR}/${PRV2}/head"
<!-- pr-versions --> Pull Request versions: | # | Base | Head | | | - | ---- | ---- | - | | 1 | 850c1ad7e3cd240e97e41fa3f1e6b38c2700106b | a8c7593204948a3ee3642c6d3dacb10bfe9df498 | [(diff)](https://forge.sourceware.org/gcc/gcc-TEST.git/compare/850c1ad7e3cd240e97e41fa3f1e6b38c2700106b...a8c7593204948a3ee3642c6d3dacb10bfe9df498) | In order to compare , clone this repository and run ``` PR=87 git fetch origin "refs/versioned_pull/${PR}/*:refs/versioned_pull/${PR}/*" PRV1=1 PRV2=2 git range-diff "refs/versioned_pull/${PR}/${PRV1}/base..refs/versioned_pull/${PR}/${PRV1}/head" "refs/versioned_pull/${PR}/${PRV2}/base..refs/versioned_pull/${PR}/${PRV2}/head" ```
forge-bot commented 2025-09-29 18:31:24 +00:00
Member
Copy link

Sent patch series version 1 containing 1 patches to gcc-patches mailing list test-list@sourceware.org and cc'd David Malcolm dmalcolm@redhat.com, jit@gcc.gnu.org.
Cover letter

Sent patch series version 1 containing 1 patches to gcc-patches mailing list <test-list@sourceware.org> and cc'd David Malcolm <dmalcolm@redhat.com>, <jit@gcc.gnu.org>. [Cover letter](https://inbox.sourceware.org/test-list/175917065126.104.5173623691448510975.batrachomyomachia.gcc.gcc-TEST.87.1.0@forge-test.rdfm.org)
antoyo commented 2025-09-29 18:57:17 +00:00
Author
Member
Copy link

@rdfm: It seems the bot will send the email for the patch with the send date being the date on the patch.
Is this expected? This could make the email harder to find in mail clients that sort by date.

@rdfm: It seems the bot will send the email for the patch with the send date being the date on the patch. Is this expected? This could make the email harder to find in mail clients that sort by date.
linaroci commented 2025-09-30 00:52:24 +00:00
First-time contributor
Copy link

CI state: success ✅
CI bot https://ci.linaro.org/job/tcwg_gnu_cross_build--master-arm-precommit/84/ : CI bot tcwg_gnu_cross_build--master-arm: Build results
See: https://ci.linaro.org/job/tcwg_gnu_cross_build--master-arm-precommit/84/artifact/artifacts/artifacts.precommit/notify/mail-body.txt

<!-- linaro-ci-status CI bot https://ci.linaro.org/job/tcwg_gnu_cross_build--master-arm-precommit/84/ --> CI state: success :white_check_mark: CI bot https://ci.linaro.org/job/tcwg_gnu_cross_build--master-arm-precommit/84/ : CI bot tcwg_gnu_cross_build--master-arm: Build results See: https://ci.linaro.org/job/tcwg_gnu_cross_build--master-arm-precommit/84/artifact/artifacts/artifacts.precommit/notify/mail-body.txt
linaroci commented 2025-09-30 18:52:49 +00:00
First-time contributor
Copy link

CI state: success ✅
CI bot https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-precommit/60/ : CI bot tcwg_gnu_cross_build--master-aarch64: Build results
See: https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-precommit/60/artifact/artifacts/artifacts.precommit/notify/mail-body.txt

<!-- linaro-ci-status CI bot https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-precommit/60/ --> CI state: success :white_check_mark: CI bot https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-precommit/60/ : CI bot tcwg_gnu_cross_build--master-aarch64: Build results See: https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-precommit/60/artifact/artifacts/artifacts.precommit/notify/mail-body.txt
rdfm commented 2025-10-01 15:37:18 +00:00
Member
Copy link

@antoyo indeed, the code in batrachomyomachia will run git format-patch and then send the generated emails without further changes to the Date.

My perl is rusty but I think what happens with git send-email is that patch emails lose the date generated by git format-patch.
I should add a ticket to sort this out.

@antoyo indeed, the code in batrachomyomachia will [run git format-patch](https://forge.sourceware.org/forge/batrachomyomachia/src/commit/f5fac826475293deabceb5f4d0b7b1eba88530cb/batrachomyomachia/local_git_ops.py#L549) and then [send the generated emails](https://forge.sourceware.org/forge/batrachomyomachia/src/commit/f5fac826475293deabceb5f4d0b7b1eba88530cb/batrachomyomachia/email.py#L81) without further changes to the Date. My perl is rusty but I think what happens with git send-email is [that patch emails lose the date generated by git format-patch](https://github.com/git/git/blob/821f583da6d30a84249f75f33501504d597bc16b/git-send-email.perl#L1571). I should add a ticket to sort this out.
linaroci commented 2025-11-01 00:25:52 +00:00
First-time contributor
Copy link

CI state: success ✅
CI bot https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-precommit/116/ : CI bot tcwg_gnu_cross_check_gcc--master-arm: Test results
See: https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-precommit/116/artifact/artifacts/artifacts.precommit/notify/mail-body.txt

Dear contributor,

Our automatic CI successfully passed with your patch(es). Please find some details below.

In  master-arm, after:
  | gcc patch https://forge.sourceware.org/gcc/gcc-TEST/pulls/87
  | Author: Antoni Boucher <bouanto@zoho.com>
  | Date:   Tue Oct 8 19:34:43 2024 -0400
  | 
  |     [PATCH] libgccjit: Handle missing types in jit_langhook_type_for_mode
  |     
  |     gcc/jit/ChangeLog:
  |     
  |             * dummy-frontend.cc: Handle new types in jit_langhook_type_for_mode.
  | ... applied on top of baseline commit:
  | a46dffee33a3 match.pd: Fold VEC_PERM_EXPR chains implementing concat-and-extract


Used configuration :
 *CI config* tcwg_gnu_cross_check_gcc master-arm
 *configure and test flags:* --target arm-linux-gnueabihf 

If you have any questions regarding this report, please ask on linaro-toolchain@lists.linaro.org mailing list.

-----------------8<--------------------------8<--------------------------8<--------------------------

The information below contains the details of the failures, and the ways to reproduce a debug environment:

You can find the failure logs in *.log.1.xz files in
 * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-precommit/116/artifact/artifacts/artifacts.precommit/00-sumfiles/
The full lists of regressions and improvements as well as configure and make commands are in
 * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-precommit/116/artifact/artifacts/artifacts.precommit/notify/
The list of [ignored] baseline and flaky failures are in
 * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-precommit/116/artifact/artifacts/artifacts.precommit/sumfiles/xfails.xfail

Current build   : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-precommit/116/artifact/artifacts
Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2409/artifact/artifacts

Warning: we do not enable maintainer-mode nor automatically update
generated files, which may lead to failures if the patch modifies the
master files.
<!-- linaro-ci-status CI bot https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-precommit/116/ --> CI state: success :white_check_mark: CI bot https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-precommit/116/ : CI bot tcwg_gnu_cross_check_gcc--master-arm: Test results See: https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-precommit/116/artifact/artifacts/artifacts.precommit/notify/mail-body.txt ``` Dear contributor, Our automatic CI successfully passed with your patch(es). Please find some details below. In master-arm, after: | gcc patch https://forge.sourceware.org/gcc/gcc-TEST/pulls/87 | Author: Antoni Boucher <bouanto@zoho.com> | Date: Tue Oct 8 19:34:43 2024 -0400 | | [PATCH] libgccjit: Handle missing types in jit_langhook_type_for_mode | | gcc/jit/ChangeLog: | | * dummy-frontend.cc: Handle new types in jit_langhook_type_for_mode. | ... applied on top of baseline commit: | a46dffee33a3 match.pd: Fold VEC_PERM_EXPR chains implementing concat-and-extract Used configuration : *CI config* tcwg_gnu_cross_check_gcc master-arm *configure and test flags:* --target arm-linux-gnueabihf If you have any questions regarding this report, please ask on linaro-toolchain@lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-precommit/116/artifact/artifacts/artifacts.precommit/00-sumfiles/ The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-precommit/116/artifact/artifacts/artifacts.precommit/notify/ The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-precommit/116/artifact/artifacts/artifacts.precommit/sumfiles/xfails.xfail Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-precommit/116/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2409/artifact/artifacts Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files. ```
linaroci commented 2025-11-14 12:06:31 +00:00
First-time contributor
Copy link

CI state: success ✅
CI bot https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-precommit/78/ : CI bot tcwg_gnu_cross_check_gcc--master-aarch64: Test results
See: https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-precommit/78/artifact/artifacts/artifacts.precommit/notify/mail-body.txt

Dear contributor,

Our automatic CI successfully passed with your patch(es). Please find some details below.

In  master-aarch64, after:
  | gcc patch https://forge.sourceware.org/gcc/gcc-TEST/pulls/87
  | Author: Antoni Boucher <bouanto@zoho.com>
  | Date:   Tue Oct 8 19:34:43 2024 -0400
  | 
  |     [PATCH] libgccjit: Handle missing types in jit_langhook_type_for_mode
  |     
  |     gcc/jit/ChangeLog:
  |     
  |             * dummy-frontend.cc: Handle new types in jit_langhook_type_for_mode.
  | ... applied on top of baseline commit:
  | 2ea9d663650 [RISC-V][PR rtl-optimization/122627] Yet another fix in IRA equivalence array handling


Used configuration :
 *CI config* tcwg_gnu_cross_check_gcc master-aarch64
 *configure and test flags:* --target aarch64-linux-gnu 

If you have any questions regarding this report, please ask on linaro-toolchain@lists.linaro.org mailing list.

-----------------8<--------------------------8<--------------------------8<--------------------------

The information below contains the details of the failures, and the ways to reproduce a debug environment:

You can find the failure logs in *.log.1.xz files in
 * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-precommit/78/artifact/artifacts/artifacts.precommit/00-sumfiles/
The full lists of regressions and improvements as well as configure and make commands are in
 * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-precommit/78/artifact/artifacts/artifacts.precommit/notify/
The list of [ignored] baseline and flaky failures are in
 * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-precommit/78/artifact/artifacts/artifacts.precommit/sumfiles/xfails.xfail

Current build   : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-precommit/78/artifact/artifacts
Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/2420/artifact/artifacts

Warning: we do not enable maintainer-mode nor automatically update
generated files, which may lead to failures if the patch modifies the
master files.
<!-- linaro-ci-status CI bot https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-precommit/78/ --> CI state: success :white_check_mark: CI bot https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-precommit/78/ : CI bot tcwg_gnu_cross_check_gcc--master-aarch64: Test results See: https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-precommit/78/artifact/artifacts/artifacts.precommit/notify/mail-body.txt ``` Dear contributor, Our automatic CI successfully passed with your patch(es). Please find some details below. In master-aarch64, after: | gcc patch https://forge.sourceware.org/gcc/gcc-TEST/pulls/87 | Author: Antoni Boucher <bouanto@zoho.com> | Date: Tue Oct 8 19:34:43 2024 -0400 | | [PATCH] libgccjit: Handle missing types in jit_langhook_type_for_mode | | gcc/jit/ChangeLog: | | * dummy-frontend.cc: Handle new types in jit_langhook_type_for_mode. | ... applied on top of baseline commit: | 2ea9d663650 [RISC-V][PR rtl-optimization/122627] Yet another fix in IRA equivalence array handling Used configuration : *CI config* tcwg_gnu_cross_check_gcc master-aarch64 *configure and test flags:* --target aarch64-linux-gnu If you have any questions regarding this report, please ask on linaro-toolchain@lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-precommit/78/artifact/artifacts/artifacts.precommit/00-sumfiles/ The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-precommit/78/artifact/artifacts/artifacts.precommit/notify/ The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-precommit/78/artifact/artifacts/artifacts.precommit/sumfiles/xfails.xfail Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-precommit/78/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/2420/artifact/artifacts Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files. ```
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u missing-types:antoyo-missing-types
git switch antoyo-missing-types

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch trunk
git merge --no-ff antoyo-missing-types
git switch antoyo-missing-types
git rebase trunk
git switch trunk
git merge --ff-only antoyo-missing-types
git switch antoyo-missing-types
git rebase trunk
git switch trunk
git merge --no-ff antoyo-missing-types
git switch trunk
git merge --squash antoyo-missing-types
git switch trunk
git merge --ff-only antoyo-missing-types
git switch trunk
git merge antoyo-missing-types
git push origin trunk
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
Compat/Breaking

Breaking change that won't be backward compatible

  
Frontend/ada

   
Frontend/c

   
Frontend/c++

   
General/forge

Forgejo infrastructure

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Library/libgcc

   
Library/libstdc++

   
Midend/gimple

   
Midend/rtl

   
Midend/tree
  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

  
Target/aarch64

   
Target/arm

   
Target/i386
  
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No labels
Compat/Breaking
Frontend/ada
Frontend/c
Frontend/c++
General/forge
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Library/libgcc
Library/libstdc++
Midend/gimple
Midend/rtl
Midend/tree
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Target/aarch64
Target/arm
Target/i386
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
gcc/gcc-TEST!87
No description provided.