What you need to know
- AMD just announced an $8 billion share repurchase program.
- The new program is in addition to a previously announced $4 billion plan that was announced in May 2021.
- The goal of the repurchase program is to offset the dilution of stocks and to reduce the amount of AMD shares.
AMD's board of directors just approved a new $8 billion share repurchase program. The new program is in addition to a similar $4 billion plan announced in May 2021. AMD should be able to offset stock dilution and reduce its overall share count with the move. It also provides an opportunity for shareholders to get a return on investment.
When AMD completed its acquisition of Xilinx, it drove the company's market cap past that of Intel. That was in large part due to the conversion of 248.38 million Xilinx shares into 428 million AMD shares. As a result of that process, there are now 1.628 billion AMD shares. The tech giant's new share repurchase program should reduce that number over time.
"We are pleased to expand our share repurchase program based on the strength of our balance sheet and expectations for future free cash flow generation," said AMD Chair and CEO Dr. Lisa Su. "With our strong financial performance, we are able to increase investments to drive long-term growth while returning additional value to our shareholders."
AMD notes in its announcement post that the program doesn't have a termination date and that it could be suspended or stopped at any time. AMD purchased approximately $3 billion worth of shares through the $4 billion program announced in May 2021.
Sean Endicott is the news writer for Windows Central. If it runs Windows, is made by Microsoft, or has anything to do with either, he's on it. Sean's been with Windows Central since 2017 and is also our resident app expert. If you have a news tip or an app to review, hit him up at email@example.com.
Get the best of Windows Central in in your inbox, every day!
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.